-
Notifications
You must be signed in to change notification settings - Fork 3
docs: add custom objects beta API documentation #96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
1e3a97d
f817a42
c20a43a
713a782
d60f276
6e378f0
dd654c9
20ddcc8
66f7b03
5020388
b4654fb
f834ec6
8ea1468
6e50d96
393a1f9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
@@ -0,0 +1,256 @@ | ||||||||||||
<Callout intent="warning"> | ||||||||||||
This functionality is in Beta. It is not recommended for use in production applications. | ||||||||||||
</Callout> | ||||||||||||
|
||||||||||||
Custom objects allow you to extend DevRev's data model beyond the standard use-cases | ||||||||||||
served by the native apps like Build and Support. Custom objects allow you to create | ||||||||||||
and manage object types tailored to your specific business needs. | ||||||||||||
|
||||||||||||
## Key concepts | ||||||||||||
|
||||||||||||
1. **Leaf type**: The base type of a custom object. For example, "campaign". | ||||||||||||
2. **Subtype**: A categorization of a leaf type. For example, "promotion" or "advertising" for a "campaign" leaf type. | ||||||||||||
3. **Schema fragment**: A schema fragment defines the schema for an object. | ||||||||||||
4. **Custom fields**: User-defined fields that store specific data for your custom object. | ||||||||||||
5. **Unique key**: A unique identifier for each custom object. This is useful for maintaining idempotency when retrying custom object creation requests. | ||||||||||||
6. **ID prefix**: A unique prefix used to generate the display ID for the custom object. If the `id_prefix` is "CAMP", the generated custom object display ID is "C-CAMP-1". The display ID is used to identify the custom object in the UI, similar to the standard DevRev object display IDs like "ISS-001" for issues. | ||||||||||||
|
||||||||||||
For more details on customization concepts, please refer to the | ||||||||||||
[Customization](./object-customization) documentation. | ||||||||||||
|
||||||||||||
## Custom object lifecycle | ||||||||||||
Let's say you want to manage marketing campaigns on DevRev. This guide goes through the process of creating a "Campaign" custom object with relevant fields. | ||||||||||||
|
||||||||||||
All DevRev objects require a schema. First, create a schema for the "Campaign" custom object. Make sure to replace the `<TOKEN>` with your API token. | ||||||||||||
|
||||||||||||
### Create a schema and a custom object | ||||||||||||
|
||||||||||||
```curl | ||||||||||||
curl --location 'https://api.devrev.ai/schemas.custom.set' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"type": "tenant_fragment", | ||||||||||||
"description": "Attributes for Campaign", | ||||||||||||
"leaf_type": "campaign", | ||||||||||||
"fields": [ | ||||||||||||
{ | ||||||||||||
"name": "name", | ||||||||||||
"field_type": "tokens", | ||||||||||||
"description": "Name of the campaign" | ||||||||||||
}, | ||||||||||||
{ | ||||||||||||
"name": "start_date", | ||||||||||||
"field_type": "date", | ||||||||||||
"description": "Start date of the campaign" | ||||||||||||
}, | ||||||||||||
{ | ||||||||||||
"name": "end_date", | ||||||||||||
"field_type": "date", | ||||||||||||
"description": "End date of the campaign" | ||||||||||||
}, | ||||||||||||
{ | ||||||||||||
"name": "budget", | ||||||||||||
"field_type": "int", | ||||||||||||
"description": "Budget allocated for the campaign" | ||||||||||||
}, | ||||||||||||
{ | ||||||||||||
"name": "target_audience", | ||||||||||||
"field_type": "enum", | ||||||||||||
"description": "Target audience for the campaign", | ||||||||||||
"allowed_values": [ | ||||||||||||
"Professionals", | ||||||||||||
"Students" | ||||||||||||
] | ||||||||||||
} | ||||||||||||
], | ||||||||||||
"is_custom_leaf_type": true, | ||||||||||||
"id_prefix": "CAMP" | ||||||||||||
Comment on lines
+68
to
+69
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we add definitions about |
||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
Note that for custom object schemas, `is_custom_leaf_type` must be set to `true` to | ||||||||||||
differentiate it from standard DevRev object schemas. | ||||||||||||
|
||||||||||||
Once the schema is created, you can create a custom object of type "Campaign": | ||||||||||||
|
||||||||||||
```curl | ||||||||||||
curl --location 'https://api.devrev.ai/custom-objects.create' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"leaf_type": "campaign", | ||||||||||||
"unique_key": "CAMP-001", | ||||||||||||
"custom_schema_spec": { | ||||||||||||
"tenant_fragment": true | ||||||||||||
}, | ||||||||||||
"custom_fields": { | ||||||||||||
"tnt__name": "Summer Sale 2023", | ||||||||||||
"tnt__start_date": "2023-06-01", | ||||||||||||
"tnt__end_date": "2023-08-31", | ||||||||||||
"tnt__budget": 10000, | ||||||||||||
"tnt__target_audience": "Professionals" | ||||||||||||
} | ||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
The response of the above API call is the ID of the custom object created. | ||||||||||||
```json {12-21} | ||||||||||||
{ | ||||||||||||
"custom_object": { | ||||||||||||
"id": "don:core:dvrv-us-1:devo/demo:custom_object/campaign/1", | ||||||||||||
"created_by": {...}, | ||||||||||||
"created_date": "2024-10-01T07:02:58.958Z", | ||||||||||||
"modified_by": {...}, | ||||||||||||
"modified_date": "2024-10-01T07:02:58.958Z", | ||||||||||||
"display_id": "C-CAMP-1", | ||||||||||||
"leaf_type": "campaign", | ||||||||||||
"unique_key": "CAMP-001" | ||||||||||||
"stock_schema_fragment": "don:core:dvrv-us-1:stock_sf/1", | ||||||||||||
"custom_schema_fragments": [ | ||||||||||||
"don:core:dvrv-us-1:devo/demo:tenant_fragment/1" | ||||||||||||
], | ||||||||||||
"custom_fields": { | ||||||||||||
"tnt__name": "Summer Sale 2023", | ||||||||||||
"tnt__start_date": "2023-06-01", | ||||||||||||
"tnt__end_date": "2023-08-31", | ||||||||||||
"tnt__budget": 10000, | ||||||||||||
"tnt__target_audience": "Professionals" | ||||||||||||
} | ||||||||||||
} | ||||||||||||
} | ||||||||||||
``` | ||||||||||||
|
||||||||||||
Note that the `id` field in the above response is the system generated unique ID for the custom object. | ||||||||||||
|
||||||||||||
The sections below provide more details on the available API endpoints for interacting with custom objects. | ||||||||||||
|
||||||||||||
### Get a custom object | ||||||||||||
|
||||||||||||
To get a custom object, use the `custom-objects.get` endpoint: | ||||||||||||
|
||||||||||||
```curl | ||||||||||||
curl --location 'https://api.devrev.ai/custom-objects.get' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"id": "don:core:dvrv-us-1:devo/demo:custom_object/campaign/1" | ||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
### List custom objects | ||||||||||||
|
||||||||||||
To list custom objects, use the `custom-objects.list` endpoint: | ||||||||||||
|
||||||||||||
```curl | ||||||||||||
curl --location 'https://api.devrev.ai/custom-objects.list' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"leaf_type": "campaign", | ||||||||||||
"filter": [ | ||||||||||||
"eq", | ||||||||||||
"$custom_fields.tnt__target_audience", | ||||||||||||
"Young adults" | ||||||||||||
] | ||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
### Update a custom object | ||||||||||||
|
||||||||||||
To update an existing custom object, use the `custom-objects.update` endpoint. The | ||||||||||||
following example updates the budget of the previously created campaign custom object: | ||||||||||||
|
||||||||||||
```curl | ||||||||||||
curl --location 'https://api.devrev.ai/custom-objects.update' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"id": "don:core:dvrv-us-1:devo/demo:custom_object/campaign/1", | ||||||||||||
"custom_fields": { | ||||||||||||
"tnt__budget": 15000 | ||||||||||||
} | ||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As discussed IRL, let's omit this as things work fine. |
||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
### Delete a custom object | ||||||||||||
|
||||||||||||
To delete a custom object, use the `custom-objects.delete` endpoint. | ||||||||||||
The following example deletes the previously created campaign custom object: | ||||||||||||
|
||||||||||||
```curl | ||||||||||||
curl --location 'https://api.devrev.ai/custom-objects.delete' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"id": "don:core:dvrv-us-1:devo/demo:custom_object/campaign/1" | ||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
## Extended use cases | ||||||||||||
bc-devrev marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||
|
||||||||||||
### Reference custom objects in other objects | ||||||||||||
Let's say you want to reference all the campaigns that have been run for a customer | ||||||||||||
workspace. You can do so by adding a field of type "id" and "id_type: custom_object.campaign" | ||||||||||||
in the account tenant schema. | ||||||||||||
|
||||||||||||
```curl {13-14} | ||||||||||||
curl --location 'https://api.devrev.ai/schemas.custom.set' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"type": "tenant_fragment", | ||||||||||||
"description": "Tenant attributes for Account", | ||||||||||||
"leaf_type": "account", | ||||||||||||
"fields": [ | ||||||||||||
{ | ||||||||||||
"name": "campaigns", | ||||||||||||
"field_type": "array", | ||||||||||||
"base_type": "id", | ||||||||||||
"id_type": [ "custom_object.campaign" ], | ||||||||||||
}, | ||||||||||||
... // other fields | ||||||||||||
], | ||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
||||||||||||
### Add subtypes to custom objects | ||||||||||||
Adding subtypes to custom objects allows you to categorize and manage your custom | ||||||||||||
objects more effectively. The process is the same as adding subtypes to other standard | ||||||||||||
DevRev objects like issues and tickets. | ||||||||||||
|
||||||||||||
Let's say you have run different types of campaigns like social media and email | ||||||||||||
marketing. You can create a subtype for each of these variants. If you want to create a | ||||||||||||
campaign custom object with subtype "social_media", you can do so as follows: | ||||||||||||
|
||||||||||||
```curl {8, 17-18} | ||||||||||||
curl --location 'https://api.devrev.ai/custom-objects.create' \ | ||||||||||||
--header 'Content-Type: application/json' \ | ||||||||||||
--header 'Accept: application/json' \ | ||||||||||||
--header 'Authorization: <TOKEN>' \ | ||||||||||||
--data '{ | ||||||||||||
"leaf_type": "campaign", | ||||||||||||
"custom_schema_spec": { | ||||||||||||
"subtype": "social_media", | ||||||||||||
"tenant_fragment": true | ||||||||||||
}, | ||||||||||||
"custom_fields": { | ||||||||||||
"tnt__name": "Summer Sale 2023", | ||||||||||||
"tnt__start_date": "2023-06-01", | ||||||||||||
"tnt__end_date": "2023-08-31", | ||||||||||||
"tnt__budget": 10000, | ||||||||||||
"tnt__target_audience": "Professionals", | ||||||||||||
"ctype__social_media_platform": "Facebook", | ||||||||||||
"ctype__post_id": "1234567890" | ||||||||||||
}, | ||||||||||||
"unique_key": "CAMP-001" | ||||||||||||
}' | ||||||||||||
``` | ||||||||||||
|
Uh oh!
There was an error while loading. Please reload this page.