# MyWebhookAPI

> Receive, store, and route webhooks via API

Base URL: https://api.mywebhookapi.com

Authentication: `Authorization: Bearer <your_api_key>`

MyWebhookAPI provides inbound webhook endpoints that store payloads and fan out to connected workflows.

## How it works
1. Create an endpoint (`POST /webhook/endpoints`) — you get back a unique slug URL.
2. Point any third-party service (Stripe, GitHub, etc.) at that URL.
3. Payloads are stored as deliveries and fan out instantly to any enabled workflows connected to that endpoint.

## Key endpoints
- `POST /webhook/endpoints` — provision a new endpoint (requires `org_id`, `name`)
- `GET /webhook/endpoints` — list all endpoints for the account
- `DELETE /webhook/endpoints/{id}` — delete an endpoint
- `GET /webhook/deliveries/{id}` — retrieve a stored delivery
- `POST /webhook/in/{slug}` — **public, no auth** — receive an inbound payload

## Integration with MyWorkflowAPI
Create a workflow at myworkflowapi.com with `trigger_config: { "endpoint_id": "<id>" }` to automatically trigger actions when this endpoint receives a payload.


## Agent Onboarding

To use this or any other MyAPIHQ service as an autonomous agent, follow these steps:

1. **Register an Agent Account**:
   Create an agent account. Returns `account_id`, `pin`, and a `token` (JWT) in one call — no email or human required.
   ```bash
   curl -X POST https://api.myapihq.com/hq/account/agent/create \
     -H "Content-Type: application/json" \
     -d '{"label": "my-agent"}'
   ```

2. **Create a Permanent API Key**:
   Use the `token` from step 1 to create a workspace-scoped API key (`hq_live_...`).
   ```bash
   curl -X POST https://api.myapihq.com/hq/account/create/key \
     -H "Authorization: Bearer <token_from_step_1>" \
     -H "Content-Type: application/json" \
     -d '{"name": "my-agent-key"}'
   ```

3. **Authenticate**:
   All subsequent requests must include: `Authorization: Bearer <your_api_key>`.
   The JWT token from step 1 is valid for account and billing endpoints only.
   All service calls (orgs, funnels, email, domains) require the API key from step 2.

## Endpoints

### POST /webhook/endpoints
**Create a webhook endpoint**
Provisions a new inbound endpoint with a unique URL. Payloads POSTed to the URL are stored and fanned out to connected workflows.

**Request Body (JSON):**
```json
{
  "org_id": string (Required),
  "name": string (Required),
  "description": string
}
```

**Response (JSON):**
```json
[Ref: Endpoint]
```

---
### GET /webhook/endpoints
**List webhook endpoints**


**Response (JSON):**
```json
Array<[Ref: Endpoint]>
```


### DELETE /webhook/endpoints/{id}
**Delete a webhook endpoint**


**Parameters:**
- `id` (path):  (type: string, Required)


### GET /webhook/deliveries/{id}
**Get a delivery**


**Parameters:**
- `id` (path):  (type: string, Required)

**Response (JSON):**
```json
[Ref: Delivery]
```


### POST /webhook/in/{slug}
**Receive a webhook payload**
Public endpoint — no authentication required. POST any JSON payload here; it will be stored and fanned out to connected workflows.

**Parameters:**
- `slug` (path):  (type: string, Required)

**Request Body (JSON):**
```json
object
```

**Response (JSON):**
```json
{
  "delivery_id": string
}
```


## Pricing

Pay per use. No subscription.

---
## Ecosystem Integration
This service is part of the MyAPIHQ ecosystem. You authenticate using an API Key generated from your MyAPIHQ account.
To view the full list of available services (like domain registration, funnel building, transactional email, object storage, etc.), fetch [https://myapihq.com/llms.txt](https://myapihq.com/llms.txt).