> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Complete guide to the Stigg REST API including authentication, common patterns, rate limits, and error handling

The Stigg REST API provides a RESTful interface for integrating with Stigg's pricing and entitlement platform. This guide covers everything you need to get started.

## Base URL

All API requests should be made to:

```
https://api.stigg.io/api/v1
```

## Request format

All requests should include the `Content-Type: application/json` header when sending a request body.

```bash theme={null}
curl -X POST "https://api.stigg.io/api/v1/customers" \
  -H "X-API-KEY: your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "customer-123",
    "name": "Acme Corp",
    "email": "billing@acme.com"
  }'
```

## Entitlements API notes

### Subscription list endpoint does not return entitlements

`GET /api/v1/subscriptions` does not include `subscriptionEntitlements` in its response. Returning full entitlement data for every subscription in a paginated list would be prohibitively expensive at scale. To retrieve entitlements for a specific subscription, use `GET /api/v1/subscriptions/{id}`. To retrieve the full entitlements defined on a plan, use `GET /api/v1/plans/{id}`.

### Subscription entitlements are overrides only

The `subscriptionEntitlements` field on `GET /api/v1/subscriptions/{id}` contains only **subscription-level overrides** (type and ID), not the full set of entitlements inherited from the plan. To retrieve all entitlements for a plan, use `GET /api/v1/plans/{planId}/entitlements`.


## Related topics

- [Introduction](/api-and-sdks/api-reference/graphql/introduction.md)