Skip to main content
POST
/
api
/
resources
/
{schemaDefinitionNameOrId}
Upload Resource
curl --request POST \
  --url https://api.embedreach.com/api/resources/{schemaDefinitionNameOrId} \
  --header 'Content-Type: application/json' \
  --data '{
  "data": {}
}'
{
  "success": true,
  "message": "<string>",
  "data": {
    "testMismatch": true,
    "nonExistentProperty": 123
  }
}

Headers

​
reach-tenant-id
string

If using a platform scoped JWT, you can pass in a header to impersonate a specific tenant to impersonate the request as.

Path Parameters

​
schemaDefinitionNameOrId
string
required

The name or id of the schema definition to upload the resource to

Query Parameters

​
onconflict
enum<string>
default:upsert

What to do if the resource already exists. upsert will merge new data with existing data (PATCH-like behavior), preserving existing fields not included in the request. Null values will delete fields. reject will throw an error if the resource already exists

Available options:
upsert,
reject
​
ignoreUnknownFields
boolean | null
default:false

Whether to allow extra fields that are not defined in the schema. If true, extra fields will be accepted but not saved. If false, requests with extra fields will be rejected.

Body

application/json
​
data
object
required

Response

Status 200 response

​
success
boolean
required
​
message
string
​
data
object