Skip to main content
POST
Describe one call on this API: its method and path, what it takes or what it returns, and the sentences the reference is written from.

Headers

Prefer
enum<string>

Preference

Available options:
params=single-object

Body

Describe one call on this API: its method and path, what it takes or what it returns, and the sentences the reference is written from.

Name the entity as well — core.assets — and a call that writes a record answers with that record's own fields, which is what goes inside its p_values, and with the name of the call that exists for that entity alone where there is one. describe_call('create_record', 'core.assets') is how to find out what adding an asset looks like.

Name a function or a read model of the api schema. The path from a request works too, with or without its query string, so /rpc/create_asset and create_asset ask the same question.

There is deliberately no way to list what exists. This answers about something you can already name, which is something you can already call — the description of this API as a whole is published as a reference document rather than served.

Needs the permission that covers integrations.

p_name
string<text>
required
p_entity
string<text>

Response

200

OK