Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/opal-stories-v1-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no email required.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
version: 2.0.0
title: Opal Stories V1 API
license:
name: Opal API License
url: https://www.workwithopal.com/api-license
description: "The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [BCP 14](https://tools.ietf.org/html/bcp14) [[RFC2119](https://tools.ietf.org/html/rfc2119)] [[RFC8174](https://tools.ietf.org/html/rfc8174)] when, and only when, they appear in all capitals, as shown here.\n\n# Other API Versions\n\nThe [v3 API](/api/documentation/v3) is less complete than the v2 API, and is still a work in progress. Currently, if a resource has endpoints in both the v2 API and the v3 API you **SHOULD** use the v2 API endpoints. At some point in the future we will recommend the v3 API instead.\n\n# Documentation Organization\n\nv2 API endpoints are categorized by stability:\n\n1. JSON:API\n2. Other\n3. Unstable\n4. Proposed\n\nv2 API endpoints in the “JSON:API”, “Unstable”, and “Proposed” categories are [JSON:API](https://jsonapi.org)-compliant ([specification](https://jsonapi.org/format/)) and can be used with any [JSON:API-compliant client](https://jsonapi.org/implementations/).\n\n<aside>\n\nTo strictly comply with the JSON:API specification your requests for endpoints in the “JSON:API”, “Unstable”, and “Proposed” categories **MUST** set the `Accept` HTTP header to `application/vnd.api+json`. The server response’s `Content-Type` HTTP header will also be `application/vnd.api+json`.\n\nYou **SHOULD** use `application/vnd.api+json` for maximum stability, but v2 API endpoints **MAY** allow the `Accept` HTTP header to be `application/json`; if so, the response’s `Content-Type` HTTP header will be `application/json`. This support for `application/json` **MAY** disappear from a given endpoint at any time, and is not available on all endpoints.\n</aside>\n\n“Other” endpoints are stable, but do not follow the JSON:API specification. (Some “Other” endpoints have data that resembles the JSON:API structure, but **MUST** be parsed as generic JSON.) Your requests **MUST** set the `Accept` HTTP header to `application/json`, and the response’s `Content-Type` HTTP header will be `application/json`.\n\n## Unstable Endpoints\n\n*Note:* This generally refers resources in the “Unstable” category, but includes endpoints with a summary that’s prefixed by `[UNSTABLE]`. These `[UNSTABLE]` endpoints may be part of a “Stable” resource.\n\nThe data structure and behavior of “Unstable” endpoints are not guaranteed, and we **MAY** change them at any time. You **MUST NOT** use these endpoints for production features, but **MAY** use them as a preview of upcoming features, and we welcome feedback.\n\n## Proposed Endpoints\n\n“Proposed” endpoints **MUST NOT** be used (they’re not yet implemented), and we **MAY** change or remove them at any time. We publish them at our discretion to share our plans and encourage internal feedback. We also welcome your feedback.\n\n# Design Principles\n\n## Breaking Changes\n\nWe **MAY** expand the data for “JSON:API” and “Other” resources, but will not change or remove existing attributes or relationships for these resources. These expansions should not require any changes to your code.\n\nWe provide no guarantees for “Unstable” and “Proposed” endpoints.\n\n## Firehose Rule\n\nBy default endpoints include all the relevant data that’s accessible to the authenticated user. Clients **MAY** specify filters, ordering, pagination, sparse fields, and other limiting mechanisms to pare down the desired data.\n\n*Note:* Existing endpoints **MAY NOT** follow this maximalist approach, but new endpoints will, and we **MAY** enhance existing endpoints.\n\n## Obscurity\n\nIn order to provide customers with as much privacy as possible, many API calls that fail authorization will return `404 Not Found` rather than `403 Forbidden`. Do not design frontends around the expectation that a `404 Not Found` status code means a resource would not be returned given different authentication credentials.\n\n# Authentication Strategies\n## OAuth 2.0\nOpal uses OAuth 2.0 (https://oauth.net/2) to authenticate users and grant access to protected resources. After registering your application as an OAuth client, you must get permission from each user before accessing their account.\n\nThe main steps are:\n\n1. Register your application\n2. Direct the user to Opal, to authorize your application\n3. Opal confirm's user identity, and asks the user to grant your application permissions\n4. Opal issues tokens your application can use to access the user's Opal resources\n5. Your application can begin making requests to the Opal API on behalf of the user\n\n### Roles\n#### Client\nThe 3rd-party application accessing the API on behalf of the User.\n\n#### API\nAPI endpoints used to interact with a User's resources in Opal.\n\n#### User\nThe person authorizing the Client to access to their Opal account.\n\n### Registering your application\nApplication registration is currently a manual process.\n\nTo begin, you will need to provide the following information to the Opal integrations team:\n\n- Application name\n- Logo URI\n- Redirect URI\n\nIn return, expect to receive:\n\n- Client ID\n - public\n- Application secret\n - keep this private\n - keep this written down someplace safe. Opal cannot retrieve this for you if it is lost.\n\n### Authorization\nFor a Client to make API requests on behalf of Users, the User must first give consent.\nHere is an overview of the consent flow:\n\n1. Direct the User to grant access in Opal\n\n```\nhttps://login.ouropal.com/oauth2/auth?grant_type=authorization_code&scope=offline_access&response_type=code&client_id={client_id}&state={state}&redirect_uri={url_encoded_redirect}\n```\n\nParameters:\n- `client_id`: Provided by Opal.\n- `grant_type`: Set the value to authorization_code to receive a code string that can be exchanged for an access token.\n- `redirect_uri`: Defined by Client. After authentication, the user will be directed to this location.\n- `response_type`: The value code should be set for refresh tokens to be issued.\n- `scope`: The value offline_access must be present if you wish to use refresh tokens.\n- `state`: Defined by the Client. A unique value used to validate the response.\n\n\n2. If logged out, User is directed to log in to Opal\n\n3. User is redirected to consent page (if the User has not already given consent)\n\n```\nhttps://login.ouropal.com/oauth2/consent?consent_challenge=abc123\n```\n\n4. If the User grants permission, User is sent to the specified `redirect_uri`\n\n```\nhttps://example.com/defined-by-client?code=Mu9z2DndN7TfXSLaf99O8ReqqXqMabXhSqP5e0jlx_Q.naLKbko-GyfPJRGYcWyclxU0sBGwygPy05OSFww0XZ8&scope=offline_access&state={state}\n```\n\nParameters:\n- `code`: The Client may use this to get an access token.\n- `scope`: API permissions granted to the Client by the User.\n- `state`: The validation string provided by the Client in step 1.\n\nIf the User declines the consent prompt, User will be sent to the same `redirect_uri`, but with an error parameter :\n\n```\nhttps://example.com/defined-by-client?error=consent+request+denied&state={state}\n```\n\nParameters:\n- `error`: A brief description of the issue.\n- `state`: The validation string provided by the Client in step 1.\n\n### Retrieving Access Token\nYou must make a POST request to the token endpoint to get an access token, before the code expires:\n\n```\ncurl -X POST \\\n https://login.ouropal.com/oauth2/token \\\n -H 'Content-Type: application/x-www-form-urlencoded' \\\n -d 'code={code}&client_id={client_id}&redirect_uri={url_encoded_redirect}&client_secret={client_secret}&grant_type=authorization_code'\n```\n\nParameters:\n- `code`\n- `client_id`: Client ID provided by Opal.\n- `client_secret`: Client secret provided by Opal.\n- `grant_type`: Set value to authorization_code .\n- `redirect_uri`: Optional.\n\nIf successful, a JSON-formatted response body will contain the access_token and refresh_token:\n\n```json\n{\n \"access_token\":\"ABC123\",\n \"token_type\":\"bearer\",\n \"expires_in\":3600,\n \"refresh_token\":\"DEF456\",\n \"scope\":\"offline_access\"\n}\n```\n\n### Refreshing an Access Token\nOnce the access_token expires, you may generate a new one at the same token endpoint, but with different parameters.\nNote that in this request, a \"refresh_token\" parameter is used instead of \"code\", and the \"grant_type\" value is now \"refresh_token\" instead of \"authorization_code\".\n\n```\ncurl -X POST \\\n https://login.ouropal.com/oauth2/token \\\n -H 'Content-Type: application/x-www-form-urlencoded' \\\n -d 'refresh_token={refresh_token}&client_id={client_id}&redirect_uri={url_encoded_redirect}&client_secret={secret}&grant_type=refresh_token'\n```\n\nParameters:\n- `client_id`: Client ID provided by Opal.\n- `client_secret`: Client secret provided by Opal.\n- `grant_type`: Set value to refresh_token .\n- `redirect_uri`: Optional.\n- `refresh_token`: Refresh token value\n\n### Making Authenticated Requests\n\nSet an authorization header in your requests, specifying your access token as documented here: https://tools.ietf.org/html/rfc6750#section-2.1.\n\n**NOTE** that the `Authorization` header supercedes the `Session-Token` header described in the documentation for many endpoints. Specifying an `Authorization` header means you do not need to specify a `Session-Token` header.\n\n```\nAuthorization: Bearer ACCESS_TOKEN\n```\n\nFor example:\n```\n GET /resource HTTP/1.1\n Host: server.example.com\n Authorization: Bearer mF_9.B5f-4.1JqM\n```\n\n### Client Revoke/Rolling OAuth secrets\nClient secrets must be kept secret and not exposed outside of the token retrieval requests. If a secret has been potentially compromised, please notify Opal as soon as possible and let us know the OAuth client id associated with the secret. We will roll/update the secret, which will invalidate all existing access and refresh tokens. Invalidating tokens will cause users to need to reauthenticate, but consent should be remembered.\n"
servers:
- url: https://login.ouropal.com
tags:
- name: Stories V1
paths:
/api/v1/stories:
post:
tags:
- Stories V1
operationId: CreateStoryV1
summary: Create a Story.
security:
- oauth2:
- offline_access
- api_key:
- Session-Token
description: Create a new Moments::Story
requestBody:
content:
application/json:
x-not-json-api: true
schema:
type: object
required:
- data
properties:
data:
type: object
required:
- type
- attributes
- relationships
properties:
type:
type: string
attributes:
type: object
required:
- description
- name
- scheduled_start_at
- scheduled_end_at
properties:
description:
type:
- string
- 'null'
description: A description of the Story.
name:
type: string
description: The name of the Story.
scheduled_start_at:
type: string
format: date-time
description: 'An ISO8601 date-time. The date and time when the Story begins.
'
scheduled_end_at:
type: string
format: date-time
description: 'An ISO8601 date-time. The date and time when the Story ends.
'
relationships:
type: object
required:
- workspace
properties:
workspace:
type: object
required:
- data
additionalProperties: false
properties:
data:
type: object
required:
- id
- type
additionalProperties: false
properties:
id:
type: string
type:
type: string
enum:
- brand
responses:
'201':
description: The story has been created
content:
application/json:
schema:
type: object
required:
- data
properties:
data:
title: story
type: object
required:
- id
- type
- attributes
- relationships
properties:
id:
type: string
pattern: ^[0-9]+$
type:
type: string
enum:
- story
attributes:
type: object
required:
- color
- description
- name
- scheduled_end_at
- scheduled_start_at
properties:
id:
type: integer
scheduled_start_at:
type: string
description: An ISO8601 date-time. Formatted as an 'Internet Date/Time' (RFC 3339).
scheduled_end_at:
type: string
description: An ISO8601 date-time. Formatted as an 'Internet Date/Time' (RFC 3339).
name:
type: string
color:
type:
- string
- 'null'
description: A hex color value with the '#' prefix.
description:
type:
- string
- 'null'
relationships:
type: object
properties:
workspace:
type: object
required:
- data
properties:
data:
type:
- object
- 'null'
required:
- id
- type
properties:
id:
type: string
type:
type: string
enum:
- workspaces
example:
data:
type: story
id: '1'
attributes:
color: '#e467d7'
description: 'The targeted marketing campaign for women''s flip flops for Spring 2020
'
name: Spring campaign
scheduled_start_at: '2020-03-01T08:00:00.000Z'
scheduled_end_at: '2020-06-01T08:00:00.000Z'
relationships:
workspace:
data:
type: workspaces
id: '1'
included:
type: workspaces
id: 1,
attributes:
name: My Workspace
slug: my_workspace
is_private: false
created_at: '2020-01-01T21:01:56.000Z'
relationships:
asset:
data: null
'400':
description: Bad request
content:
application/json:
x-not-json-api: true
schema:
type: object
required:
- errors
properties:
errors:
type: array
example:
errors:
- data[attributes][scheduled_start_at] is missing
put:
tags:
- Stories V1
operationId: UpdateStoryV1
summary: Update a Story.
security:
- oauth2:
- offline_access
- api_key:
- Session-Token
description: Update attributes in an existing Moments::Story
requestBody:
content:
application/json:
x-not-json-api: true
schema:
type: object
required:
- data
properties:
data:
type: object
required:
- type
- attributes
- relationships
properties:
type:
type: string
attributes:
type: object
required:
- description
- id
- name
- scheduled_start_at
- scheduled_end_at
properties:
description:
type:
- string
- 'null'
description: A description of the Story.
id:
type:
- string
- 'null'
description: The id of the story to be updated.
name:
type: string
description: The name of the Story.
scheduled_start_at:
type: string
format: date-time
description: 'An ISO8601 date-time. The date and time when the Story begins.
'
scheduled_end_at:
type: string
format: date-time
description: 'An ISO8601 date-time. The date and time when the Story ends.
'
relationships:
type: object
required:
- workspace
properties:
workspace:
type: object
required:
- data
additionalProperties: false
properties:
data:
type: object
required:
- id
- type
additionalProperties: false
properties:
id:
type: string
type:
type: string
enum:
- brand
responses:
'200':
description: The story has been updated
content:
application/json:
schema:
type: object
required:
- data
properties:
data:
title: story
type: object
required:
- id
- type
- attributes
- relationships
properties:
id:
type: string
pattern: ^[0-9]+$
type:
type: string
enum:
- story
attributes:
type: object
required:
- color
- description
- name
- scheduled_end_at
- scheduled_start_at
properties:
id:
type: integer
scheduled_start_at:
type: string
description: An ISO8601 date-time. Formatted as an 'Internet Date/Time' (RFC 3339).
scheduled_end_at:
type: string
description: An ISO8601 date-time. Formatted as an 'Internet Date/Time' (RFC 3339).
name:
type: string
color:
type:
- string
- 'null'
description: A hex color value with the '#' prefix.
description:
type:
- string
- 'null'
relationships:
type: object
properties:
workspace:
type: object
required:
- data
properties:
data:
type:
- object
- 'null'
required:
- id
- type
properties:
id:
type: string
type:
type: string
enum:
- workspaces
example:
data:
type: story
id: '1'
attributes:
color: '#e467d7'
description: 'The targeted marketing campaign for women''s flip flops for Spring 2020
'
name: Spring campaign
scheduled_start_at: '2020-03-01T08:00:00.000Z'
scheduled_end_at: '2020-06-01T08:00:00.000Z'
relationships:
workspace:
data:
type: workspaces
id: '1'
included:
type: workspaces
id: 1,
attributes:
name: My Workspace
slug: my_workspace
is_private: false
created_at: '2020-01-01T21:01:56.000Z'
relationships:
asset:
data: null
'400':
description: Bad request
content:
application/json:
x-not-json-api: true
schema:
type: object
required:
- errors
properties:
errors:
type: array
example:
errors:
- data[attributes][scheduled_start_at] is missing
components:
securitySchemes:
oauth2:
type: oauth2
description: This API uses OAuth 2.0 with the authorization code grant flow. You can find more detailed authentication instructions in the [Authentication Strategies](/api/documentation#section/Authentication-Strategies/OAuth-2.0) section.
flows:
authorizationCode:
authorizationUrl: /oauth2/auth
tokenUrl: /oauth2/token
scopes:
offline_access: Include this scope if you wish to receive a refresh token
api_key:
type: apiKey
description: (Deprecated) This API also supports authentication via an API or session token set in the request headers.
in: header
name: Session-Token
x-tagGroups:
- name: JSON:API
tags:
- Accounts
- Activities
- Annotations
- Asset Reference Options
- Asset Reference Usage Rights Options
- Asset References
- Assets
- Brand Settings
- Brands
- Checkpoints
- Content
- Delivery Records
- Label Sets
- Labels
- Messages
- Moments
- Phase Items
- Placements
- Post Types
- Privacy
- Reactions
- Rich Texts
- Services
- Stamps
- Stories
- Url Uploads
- User Domain Views
- Users
- Workflows
- name: Other
tags:
- Budgets
- URL Previews
- Search
- Stories V1
- name: ⚠️ Unstable
tags: []
- name: Additional Resources
tags:
- secondary_resources