Target Admin API Offer creation not in UI

4 replies
226 views
Translate All

When using the Target Admin API, I’m creating new JSON offers. My requests are returning a ‘201 Created’ response, but when looking at the Target UI, I’m not seeing the offers in the default workspace. I can confirm that the API has access to the correct workspaces, and response shows the offer created in workspace: default.

The response also shows an OfferId that looks accurate.

Additionally, some time has passed (>60 minutes), and no offer has appeared yet.

Should the Offers be accessible from the Target UI after creation with the API?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

johnsi11

Level 2

When you successfully create the offer, does the response give you an offer ID back? If yes, are you the able to request that offer via the API by that ID and receive a response?

Translate

A

ALB15

Level 2

@johnsi11 Yes, the Get json offer by ID request does return the same offer that I initially created.

{

"id": 867112,

"name": "Test Offer",

"content": {

"html": "<div>Hello </div>"

},

"workspace": "xxxxx",

"modifiedAt": "2026-05-07T13:19:49Z"

}

This is to fetch: https://developer.adobe.com/target/administer/admin-api/#tag/Offers/operation/getOffer_1

This to create: https://developer.adobe.com/target/administer/admin-api/#tag/Offers/operation/createOffer_1

Translate

johnsi11

Level 2

Offers created by the API should be visible in the UI, it's often not as instant as the UI, but they should show up within a few minutes.

It looks like you're creating the offer correctly so the offer is going somewhere. I’m assuming that you've double checked the API credentials match the the target organization, client, & tenant that you're looking at in the UI, you're sending things to the default workspace, there's no property filter in the UI, etc. Have you tried clearing your cache and cookies, signing out and signing back in?

Translate

SuryaLakhani

Level 4

Hi, try setting the specific workspace ID instead of letting it set to default, as Johnsi11 mentioned they might be going to some other workspace.

Translate

Sign up

Login with SSO

Login to the community

Login with SSO