how do I get Unsuppress Profiles API to work consistently?

Hi Brian, 

Happy to jump in and answer this for you! 

Your formatting looks correct from what I can see- example:

{
  "data": {
    "type": "profile-suppression-bulk-delete-job",
    "attributes": {
      "profiles": {
        "data": [
          {
            "type": "profile",
            "attributes": {
              "email": "example@klaviyo-demo.com"
            }
          }
        ]
      }
    }
  }
}
'

The issue is the job response/processing, not the JSON syntax.

Key indicators:

• The job returns status: "processing" but also sets completed_at almost immediately.
• total_count, completed_count, and skipped_count are all 0, meaning the job did not register the profile as processed.
• It sounds like your team is treating the initial POST response as confirmation that the profile was unsuppressed. This endpoint is asynchronous; you must poll the returned job URL until processing completes. Bulk jobs can experience delays between acceptance and actual processing.
• Unsuppression only removes eligible non-deliverability/manual suppressions. It will not remove hard-bounce or invalid-email suppressions.
• A possible contributing factor is repeated one-profile requests. Klaviyo has documented system strain from accounts creating many single-profile suppression jobs; batching profiles is the recommended pattern.

So the likely issue is either an asynchronous processing incident/backlog or the profile has a suppression reason that this endpoint cannot remove. The next diagnostic step is to retrieve the job status and inspect the profile’s exact suppression reason.

My problem was in the UI as well.  For some reason the UI gives the option to Unsuppress but most of the profiles result in error like this when trying to unsuppress manually:  

Hi Brian, 
Thank you for letting us know! I am going to follow up with you in a direct message on this concern to determine the behavior, resolution, and gather more relevant details to take a look at this!