Surfboard API (unstable)

Download OpenAPI specification:Download

This is the API specification for Surfboard. Our API is JSON-encoded and follows a REST style.

Authentication

To access the API, you can reach out to your customer success manager who will provide you securely with an access token which is valid for one year.

This token should be included in any requests you make to Surfboard’s API in the Authorization header in 'bearer token' format, like so:

curl 'https://api.teamsurfboard.com/...' \
  -H 'Authorization: Bearer ...'

API requests without authentication will fail.

Rate limiting

The API enforces a rate limit of 60 requests per minute to ensure stability. Once this limit is exceeded, the API will respond with a status code of 429.

Versioning

Over time, new endpoints will be made available and existing endpoints may evolve, but backwards compability will be maintained. Fields will not be removed from response payloads, but new fields may be added to existing endpoints.

Any backwards-incompatible changes will be made in a new version of the API, and existing versions will remain functional.

Get schedule

Returns the published schedule within the specified date range.

query Parameters
start
required
string
Example: start=2024-06-25T00:00:00.000Z

A date string in RFC 3339 format.

end
required
string
Example: end=2024-06-25T00:00:00.000Z

A date string in RFC 3339 format.

page[size]
number
Default: 100

The maximum number of entities to be returned in one response.

page[after]
string

The pagination cursor to be used for the next response. If a response has more than one page, the full URL for the next page (including the appropriate page[after] parameter) will be included in the /links/next field in the response payload.

Responses

Response samples

Content type
application/json
{
  • "data": [
    ],
}

Get tasks

Returns a list of all tasks.

query Parameters
page[size]
number
Default: 100

The maximum number of entities to be returned in one response.

page[after]
string

The pagination cursor to be used for the next response. If a response has more than one page, the full URL for the next page (including the appropriate page[after] parameter) will be included in the /links/next field in the response payload.

Responses

Response samples

Content type
application/json
{
  • "data": [
    ]
}