- Documentation
- API Reference
- Case Studies
- Security Trust Center
- Changelog
- Customer Endpoints
- GETGet All
- POSTGet or Create
- POSTUpdate
- DELDelete
- POSTRefresh Token
- POSTConfigure Portal
- POSTGenerate JWT
- Resource Endpoints
- GETList Team Dashboards
- GETList Team Report Builders
- POSTPublish to Environment
- POSTEmail Dashboard Screenshot as Attachment
- POSTEmail Dashboard Report
- End User Group Endpoints
- POSTGet or Create
- POSTUpdate
- DELDelete
- POSTRefresh Token
Customer API
Resource API
End User Group API [Deprecated]
Refresh Customer Token
This is the current customer token you have for the customer that you want to rotate.
curl --location --request POST 'https://api.explo.co/api/update_customer/' \
--header 'Content-Type: application/json' \
--header 'Explo-Authorization: Token <token>' \
--data-raw '{
"current_token": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}'
{
"success": 1,
"customer": {
"token": "<customer_token_to_auth_dashboard>",
"name": "Example 1",
"provided_id": "example_1",
"is_demo_group": false,
"emails": ["[email protected]"],
"properties": { "filterValue": "new_value" },
"computed_properties": { "filterValue": "new_value" },
"parent_schema_datasource_mapping": {"40": "213": "134": 386"},
"computed_parent_schema_datasource_mapping": {"40": "213": "134": 386"}
}
}
This endpoint refreshes a customer token. This is useful when you want to force a customer token to rotate because an existing one may be compromised.
Body
This is the current customer token you have for the customer that you want to rotate.
Response
Indicates whether the call was successful. 1 if successful, 0 if not.
The contents of the customer
The customer token (customerToken or CUSTOMER_TOKEN) that will be used to identify which customer is viewing the dashboard. You should save this on your end to use when rendering an embedded dashboard by passing this token into the web component or iframe. Example usage here.
The display name you provided for your customer in Explo.
The ID you use to identify this customer in your database that you provided. This is also the ID you will use to reference your customer in Explo queries or access your customer via the API. For more information on example usage, check out this section.
An array of email addresses you provided for your customer.
True if this customer is a demo customer, which means that data panels will include a demo watermark for the customer. Demo customers do not count towards paid customers.
A set of key-value pairs assigned to this customer. These will be accessible through variables in the dashboards and SQL editor. More information on properties can be found in this section.
A properties object based on the provided properties of this customer and any inherited properties from parent customers.
A set of key-values pairs that map a schema id to the data source that this customer loads data from. For more information on schemas and data sources, check out this section.
A schema datasource mapping object based on the parent_schema_datasource_mapping of the customer and any inherited parent_schema_datasource_mapping from parent customers.
curl --location --request POST 'https://api.explo.co/api/update_customer/' \
--header 'Content-Type: application/json' \
--header 'Explo-Authorization: Token <token>' \
--data-raw '{
"current_token": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}'
{
"success": 1,
"customer": {
"token": "<customer_token_to_auth_dashboard>",
"name": "Example 1",
"provided_id": "example_1",
"is_demo_group": false,
"emails": ["[email protected]"],
"properties": { "filterValue": "new_value" },
"computed_properties": { "filterValue": "new_value" },
"parent_schema_datasource_mapping": {"40": "213": "134": 386"},
"computed_parent_schema_datasource_mapping": {"40": "213": "134": 386"}
}
}