Data 360: Formatting IDs for Streaming Ingestion API DELETE Calls

1. Case Sensitivity: Primary Keys are case-sensitive. This means that the uppercase and lowercase letters within the ID are considered distinct. Ensure the ID you include in your DELETE call exactly matches the case of the ID present in Data 360 (formerly Data Cloud).
2. Identify Special Characters: Review the Primary Key of the record you want to delete. Look for any characters that aren't alphanumeric (a-z, A-Z, 0-9) or underscores (_). These characters might need encoding.
3. Encode Special Characters: Use the percent encoding format (%XX), where XX is the hexadecimal code of the special character. You can find online tools or resources to help you convert the special character to its hexadecimal code.
4. Update DELETE Call: Replace the special character in your Primary Key with its encoded version within the DELETE call.

For instance, if your original Primary Key contains "Item+123", the encoded version might be "Item%2B123".

Thus, the URl to delete the above record would be:
https://{instance_url}/api/v1/ingest/sources/{name}/{object-name}?ids=Item%2B123

[Uncommon Use Case]:
Ingestion Api doesn't have a guard rail to prevent users from ingesting bad data for example, data with emojis or different language characters. This is up to the user to look over their data before ingesting it into Data 360.

If user do ingest bad data and want to delete it. Please proceed to use the Bulk delete API. No need to convert the characters into UTF-8, with the bulk delete api, you can just send in emojis or special character in the body of the request to delete the appropriate bad data.

For example, if the Primary key = 💪👌 you can proceed with using the bulk api to delete these primary key by adding  💪👌 in the body. No need to decode them.

Walkthrough here of bulk ingestion api job creation and operations: https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_bulk_insert_example.htm