Target API error - created only Adobe Target Classic

[johnt54373251]

Dears

I'm using Target API to create activity, I found that I can only create  Adobe Target Classic activity through the API.

Can someone correct my error, thank you!

{

    "id": 217152,

    "name": "215888.hotel6",

    "state": "approved",

    "priority": 1,

    "options": [

        {

            "optionLocalId": 2,

            "name": "Offer2",

            "offerId": 456717

        }

    ],

    "locations": {

        "mboxes": [

            {

                "locationLocalId": 0,

                "name": "hompageCarousel"

            }

        ]

    },

    "experiences": [

        {

            "experienceLocalId": 0,

            "name": "Experience A",

            "visitorPercentage": 100,

            "optionLocations": [

                {

                    "locationLocalId": 0,

                    "optionLocalId": 2

                }

            ]

        }

    ],

    "metrics": [

        {

            "metricLocalId": 32767,

            "name": "MY PRIMARY GOAL",

            "conversion": true,

            "engagement": "page_count",

            "action": {

                "type": "count_once"

            },

            "mboxes": [

                {

                    "name": "target-global-mbox",

                    "successEvent": "mbox_shown"

                },

                {

                    "name": "hompageCarousel",

                    "successEvent": "mbox_shown"

                }

            ]

        }

    ],

    "modifiedAt": "2018-03-13T10:52:35Z"

}

[siddharthjainPM · Accepted solution]

Hi John

Target Classic has been phased off. Its no longer accessible via UI. If however, Classic API call is made (looks like your organization has been granted extension to migrate off of Classic APIs to Adobe.io), then yes, activities will get created.

Please check out Target API​ page for the newer way to create activities via APIs through Adobe.io Gateway

[bkmills1]

Hello Siddharth,

I'm experiencing the same thing, however, I followed the steps to create an Offer by setting up the Adobe I/O integration. After generating my JWT and using the curl script, I was able to create an offer via Postman, but like John describes, it's shown as coming from Target Classic. Our organization hasn't used Target Classic since before its decommission.

I should note that, this doesn't appear to cause any problems, as I was able to select the offer from within a test activity. Just wondering what the potential side affects are?

Thanks,

Brion

[tanvia28417128]

Hi.

I believe there are no side effects of the activities being displayed as coming from target classic. This appear to be happening as your organization has been granted an extension to migrate off of Classic APIs to Adobe.io