admin5

apikeys6

apps7

authproviders7

billing2

custom-user-data2

data-api4

dependencies1

deploy13

email3

endpoints5

environments6

event-subscriptions3

functions7

graphql10

hosting7

log_forwarders7

logs1

metrics1

notifications7

rules9

schemas8

secrets4

security15

services11

sync2

triggers6

users12

values5

webhooks5

graphql

Get a custom resolver

Get a specific custom resolver configuration.

get/groups/{groupId}/apps/{appId}/graphql/custom_resolvers/{customResolverId}

Response

OK

on_typestring required

The name of the resolver's parent type. This can be "Query", "Mutation", or the name of a generated type if this is a computed property.

field_namestring required

The name of the custom resolver field that appears in the GraphQL schema.

input_type_format'scalar' | 'scalar-list' | 'generated' | 'generated-list' | 'custom'

The kind of input type the custom resolver uses. This value must agree with the value of input_type:

A scalar input type must use "scalar" or "scalar-list"
A generated input type must use "generated" or "generated-list"
A custom input type must use "custom"

If undefined, the resolver does not accept an input.

payload_type_format'scalar' | 'scalar-list' | 'generated' | 'generated-list' | 'custom'

The kind of payload type the custom resolver uses. This value must agree with the value of payload_type:

A scalar payload type must use "scalar" or "scalar-list"
A generated payload type must use "generated" or "generated-list"
A custom payload type must use "custom"

If undefined, the resolver returns a DefaultPayload object.

_idstring required

The custom resolver's unique ID.

function_idstring required

The resolver function's unique ID.

Changes

Changed in 1 of the 50 revisions of this API.541

Feb 20, 2024v3e2240dd053bd541See the full diff
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  removed the required property from the response with the status
  response-required-property-removed
- ▲
  removed the required property from the response with the status
  response-required-property-removed
- ▲
  removed the required property from the response with the status
  response-required-property-removed
- ▲
  removed the required property from the response with the status
  response-required-property-removed
- ●
  removed the optional property from the response with the status
  response-optional-property-removed
- ●
  removed the optional property from the response with the status
  response-optional-property-removed
- ●
  removed the optional property from the response with the status
  response-optional-property-removed
- ●
  removed the optional property from the response with the status
  response-optional-property-removed
- ○
  added subschema #2 to the response body allOf list for the response status
  response-body-all-of-added
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog