Skip to main content
PUT
/
tenant
/
{env_id}
/
{tenant}
/
mapping
Set tenant mapping
curl --request PUT \
  --url https://api.hotglue.com/tenant/{env_id}/{tenant}/mapping \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "entityId": "<string>",
  "flow": "<string>"
}
'
{}

Documentation Index

Fetch the complete documentation index at: https://docs.hotglue.com/llms.txt

Use this file to discover all available pages before exploring further.

You can use the Set Tenant Mapping endpoint to apply a mapping without using the mapping widget.
If the Update Fields on Mapping widget setting is enabled, the optional entityType, entityId, and flow params are required.
Below is an example body: 
{
  "config": {
    "mapping": {
      "<FlowId>": {
        "<InternalTableName>/<RemoteTableName>": {
          "<InternalField>": "<RemoteField>" 
        }
      }
    }
  },
  "entityType": "taps", // optional - `taps` or `connectors`
  "entityId": "salesforce", // optional
  "flow": "FElWoODnU" // optional
}

Authorizations

​
x-api-key
string
header
required

Path Parameters

​
env_id
string
required

ID of environment

​
tenant
string
required

ID of tenant

Body

application/json
​
config
object
​
entityType
enum<string>

Optional. Use taps for one-way flows, and connectors for bi-directional flows.

Available options:
taps,
connectors
​
entityId
string

Optional. Identifier for the tap/connector (e.g., "salesforce").

​
flow
string

Optional. Flow ID that this operation pertains to.

Response

200

The response is of type object.