How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Adobe Suite Challenges API

Manage the creation, updating, deleting, and retrieval of Challenges

Adobe Suite Challenges API is one of 482 APIs that Adobe Suite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Challenges. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, release notes, and a getting-started guide.

This API exposes 11 operations across 7 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 3 base URLs: http://localhost:8081, https://loyalty-metadata-service-stage2.corp.ethos12-stage-va7.ethos.adobe.net, https://platform.adobe.io/ajo.

11 operations 7 paths 24 schemas 1 DELETE2 GET1 PATCH6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://image.adobe.io
Resource Areas
1

Paths & Operations 11

Across 7 paths, the API surfaces 11 operations — 1 DELETE, 2 GET, 1 PATCH, 6 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Challenges 11

Manage the creation, updating, deleting, and retrieval of Challenges

GET
/loyalty/metadata/challenges/{challengeId}
Retrieve a Challenge by its challengeId
readOne_1 7 params → 200400401404409422500
PUT
/loyalty/metadata/challenges/{challengeId}
Replace an existing challenge by overwriting
update_1 7 params body → 200400401404409422500
DELETE
/loyalty/metadata/challenges/{challengeId}
Delete a challenge and its associated journey
delete_1 7 params → 200400401404409422500
PATCH
/loyalty/metadata/challenges/{challengeId}
Patch an existing challenge by root keys if present
patch_1 7 params body → 200400401404409422500
GET
/loyalty/metadata/challenges
Retrieve all Challenges with filtering and sorting
readMany_1 10 params → 200400401404409422500
POST
/loyalty/metadata/challenges
Create a Challenge
create_1 6 params body → 200400401404409422500
POST
/loyalty/metadata/challenges/{challengeId}/unpublish
Unpublish a Challenge and make it unavailable to your customers
unPublish 7 params → 200400401404409422500
POST
/loyalty/metadata/challenges/{challengeId}/publish
Publish a Challenge and make it available to your customers
publish 8 params → 200400401404409422500
POST
/loyalty/metadata/challenges/{challengeId}/duplicate
Duplicate a challenge including journey metadata and campaigns
duplicate 7 params → 200400401404409422500
POST
/loyalty/metadata/challenges/{challengeId}/archive
Archive a Challenge. Once in this state, the challenge can only be deleted.
archive 7 params → 200400401404409422500
POST
/loyalty/metadata/challenges/initialize
Initialize shell journey & challenges
initialize 6 params body → 200400401404409422500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Challenge (37 properties), Task (20 properties), PersonalizedTaskAttributes (10 properties), MessageConfig (8 properties). Each schema is shown below with its type and property counts.

ContentPhaseConfig
object
Message sequence for a journey phase
1 property
Daypart
object
2 properties
Reward
object
3 properties
ProblemDetail
object
6 properties
ChallengeList
object
1 property
Variables
object
8 properties
AudienceQualificationConfig
object
Audience configuration for journey targeting
2 properties 1 required
Challenge
object
37 properties
Milestone
object
3 properties
PurchaseTask
IncludeExclude
object
2 properties
PersonalizedAttributes
object
5 properties
MetadataConfig
object
Journey metadata for context and challenge linking
5 properties 2 required
JourneyMetadata
object
Journey configuration for challenge journeys
4 properties 3 required
EventTemplatesConfig
object
3 properties
PersonalizedTaskAttributes
object
10 properties
ContentConfig
object
Content phases for journey messaging
3 properties
Schedule
object
2 properties
MessageConfig
object
Message configuration for a journey node
8 properties 2 required
DependsOn
object
1 property
TaskTemplate
object
2 properties
EventTemplateDetail
object
Event definition for journey progression
4 properties 2 required
Task
object
20 properties
MilestoneReward
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adobe-suite-challenges-api-openapi.yml Raw ↑

Other APIs Adobe Suite publishes across the network.

Adobe Sign API
Adobe Experience Manager API
Adobe Stock API
Adobe Premiere Pro API
Adobe After Effects API
Adobe Target API
Adobe Campaign API
Adobe User Management API
Adobe I/O Events API
Adobe MCP Servers
Adobe Suite Accelerated Queries API
Adobe Suite Access Control Policies API
Where this information came from

This is an independent, third-party profile of Adobe Suite Challenges API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.