# API Overview
> Source: /api-reference/introduction/overview
> Journey APIs for members, partners, administrators, internal services, and public access

# Journey API Overview [#journey-api-overview]

The Journey API provides product APIs for members, partners, administrators,
internal services, and public experiences. The Core Platform guides organize
durable operational contracts across the protected route surfaces.

## API Surfaces [#api-surfaces]

<CardGroup cols={2}>
  <Card title="Members API" icon="user" href="/api-reference/members/overview">
    Customer-facing endpoints for profile, loyalty, and reservations
  </Card>
  <Card title="Admin API" icon="shield">
    Administrative operations for member and reservation management
  </Card>
  <Card title="Partner API" icon="building-2" href="/api-reference/partner/overview">
    Scoped partner operations, fulfillment, guests, and property workflows
  </Card>
  <Card title="Public API" icon="globe" href="/api-reference/public/overview">
    Unauthenticated access to property and reservation information
  </Card>
  <Card title="Core Platform" icon="network">
    Commercial, usage, accounting, Rain, Insights, and Intelligence contracts across partner, admin, and internal routes
  </Card>
  <Card title="HXP Threads & Actions" icon="messages-square" href="/hxp/overview">
    Guest conversations, event polling, Action commands, and the separate operator MCP integration boundary
  </Card>
</CardGroup>

<Note>
  Core Platform is a domain-oriented guide, not a separate public credential or
  hostname. Its endpoints use `/partner/*`, `/admin/*`, and `/internal/*`
  according to the caller and trust boundary.
</Note>

## Base URLs [#base-urls]

| Environment | URL |
|------------|-----|
| Production | `https://api-prd.cf.journey.com/v1` |
| Development | `https://api-dev.cf.journey.com/v1` |

<Note>
  [HXP Threads and Actions](/hxp/overview) use `https://v3.hxp.journey.com`,
  different authentication, and explicit response envelopes. The base URLs and
  response format below apply to the Journey API surfaces above, not HXP.
</Note>

## Response Format [#response-format]

Responses return the resource directly as a JSON object or array — no wrapper envelope.

## Error Handling [#error-handling]

Errors return standardized HTTP status codes with a consistent error body:

```json
{
  "type": "BadRequestException",
  "timestamp": "2026-04-21T17:45:09.534Z",
  "code": null,
  "message": "Validation failed (uuid is expected)"
}
```

## Rate Limiting [#rate-limiting]

Existing documented API surfaces use a default limit of 100 requests per
minute. Endpoint-specific bounds may also apply. Respect `Retry-After` when
present and use stable idempotency keys for Core mutations.

## Support [#support]

For API issues, post in [#team-engineering](https://slack.com/app_redirect?channel=C095V29B493) on Slack.

- [Support](mailto:api-support@journey.com)