How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Atomic Webhooks API

The Webhooks API from Atomic — 2 operation(s) for webhooks.

Atomic Webhooks API is one of 9 APIs that Atomic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Webhook. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://api.atomicfi.com, https://sandbox-api.atomicfi.com, https://pci.atomicfi.com, https://sandbox-pci.atomicfi.com.

4 operations 2 paths 3 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.atomicfi.com
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Atomic Webhooks API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). An API key is passed in the header as x-public-token (PublicTokenAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API Key sent in the x-api-key header, paired with the x-api-secret header. Used for backend-to-backend calls.
  • PublicTokenAuth — Public token for permitted client-side requests.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Webhooks 4
GET
/webhooks/endpoints
List webhook endpoints
listWebhookEndpoints → 200
POST
/webhooks/endpoints
Create a webhook endpoint
createWebhookEndpoint body → 200
PUT
/webhooks/endpoints/{id}
Update a webhook endpoint
updateWebhookEndpoint 1 param body → 200
DELETE
/webhooks/endpoints/{id}
Delete a webhook endpoint
deleteWebhookEndpoint 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are WebhookEndpoint (3 properties), WebhookEndpointRequest (3 properties), SuccessResult (2 properties). Each schema is shown below with its type and property counts.

SuccessResult
object
2 properties
WebhookEndpointRequest
object
3 properties 2 required
WebhookEndpoint
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

atomic-fi-webhooks-api-openapi.yml Raw ↑

Other APIs Atomic publishes across the network.

Atomic Access Tokens API
Atomic Company API
Atomic Data API
Atomic Linked Accounts API
Atomic PayLink API
Atomic Secrets API
Atomic Tasks API
Atomic Users API
Where this information came from

This is an independent, third-party profile of Atomic Webhooks API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.