# API reference (/docs/api-reference)





The interactive reference lists Eventlayer’s HTTP operations, request bodies and
response schemas. [Start with the quickstart](/docs/quickstart) if you are making
your first call.

<DocsLinks
  items="[
{ title: &#x22;Open the interactive API reference&#x22;, description: &#x22;Browse endpoints and their request and response schemas.&#x22;, href: forgeBaseUrl },
{ title: &#x22;TypeScript SDK&#x22;, description: &#x22;Use typed resource methods, result envelopes and pagination.&#x22;, href: &#x22;/docs/sdk&#x22; },
]"
/>

## Authentication [#authentication]

Use your server-side API key for API requests. Manage keys and webhook endpoints
in the dashboard. Incoming webhooks use a separate signing secret.
See [authentication](/docs/authentication).

## SDK and HTTP field names [#sdk-and-http-field-names]

SDK input uses camelCase, such as `attendeeId` and `startAt`. HTTP request bodies
use fields such as `attendee_id` and `start_at`. Resource responses retain the
HTTP field names. Examples label their language and execution context.

## Handle the response [#handle-the-response]

The SDK returns `{ data, error, response }`. Inspect `error` before using `data`.
Network failures throw. Raw HTTP responses have their own status and response
envelope; the interactive reference documents those schemas.

Use [errors and request IDs](/docs/errors), [pagination](/docs/pagination) and
[retries and recovery](/docs/retries) when building your integration.