Skip to main content

Overview

The API Request step lets you call any external API or web service. Configure the method, URL, headers, authentication, and body to integrate with third-party services or internal APIs.

Configuration

FieldOptions
MethodGET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
URLTarget endpoint (supports template variables)
HeadersKey-value header pairs
Query ParamsKey-value query parameters
AuthNone, Basic Auth, Bearer Token, API Key, OAuth2, Royaltyport API
BodyNone, Text (JSON / XML / Raw), or Form (with multipart toggle)

Authentication

Select an auth type to attach credentials from your secrets to the request:
Auth TypeDescription
NoneNo authentication
Basic AuthHTTP basic authentication (username + password)
Bearer TokenBearer token in the Authorization header
API KeyCustom API key header
OAuth2OAuth2 client credentials flow
Royaltyport APIBuilt-in authentication for the Royaltyport REST API

Royaltyport API

The Royaltyport API auth type lets you call the Royaltyport REST API directly from your automations without managing tokens or secrets. Authentication is handled automatically using your project’s internal credentials — no setup required. Select Royaltyport API from the auth dropdown and point the URL at any https://api.royaltyport.com/v1/ endpoint. The step injects the correct authorization headers at runtime. To get started quickly, use one of the built-in Royaltyport presets:
PresetEndpoint
Royaltyport — List ProjectsGET /v1/projects
Royaltyport — Get ProjectGET /v1/projects/:id
Royaltyport — Search ProjectGET /v1/projects/:id/search
Royaltyport — List ContractsGET /v1/contracts
Royaltyport — Get ContractGET /v1/contracts/:id
Royaltyport — List EntitiesGET /v1/entities
Royaltyport — Get EntityGET /v1/entities/:id
Royaltyport — List ArtistsGET /v1/artists
Royaltyport — Get ArtistGET /v1/artists/:id
Royaltyport — List WritersGET /v1/writers
Royaltyport — Get WriterGET /v1/writers/:id
Presets fill in the URL, headers, and auth automatically. Combine them with trigger data like {{trigger.contract_id}} to make them dynamic.
See the full API Reference for all available endpoints and response schemas.

Body Types

TypeDescription
NoneNo request body (typically for GET requests)
TextRaw text body with format selector (JSON, XML, or Raw)
FormForm data with key-value pairs and optional multipart toggle for file uploads

Output

FieldTypeDescription
statusnumberHTTP status code
headersobjectResponse headers
bodyanyResponse body
errorbooleanWhether an error occurred
error_messagestringError description if failed