Skip to content

CCSAAS-2663: Get credential flow for ACCS REST API (phase 1) #462

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 8 commits into from

Conversation

jeff-matthews
Copy link
Contributor

@jeff-matthews jeff-matthews commented Jul 11, 2025

Purpose of this pull request

This pull request (PR) implements the GetCredential component for the Adobe Commerce as a Cloud Service REST API.

It seeks to cover the simplified requirements for phase 1 implementation as discussed in #459.

Staging

Note

Requires VPN if remote for proper rendering.

https://developer-stage.adobe.com/commerce/webapi/reference/rest/saas/

TODOs

  • As soon as we get template IDs from the Developer Platform team, we can update this PR and start testing.
  • Redocly registry clean up:
    • Remove branch/PR validation
    • Remove hosted docs

whastnew
Enabled a workflow to allow users to get credentials to try the Adobe Commerce as a Cloud Service REST API directly from the reference documentation.

@jeff-matthews jeff-matthews self-assigned this Jul 11, 2025
@jeff-matthews jeff-matthews added enhancement New feature or request major-update Significant updates to content internal Differentiates work between community and Adobe staff labels Jul 11, 2025
@jeff-matthews
Copy link
Contributor Author

jeff-matthews commented Jul 11, 2025

When I try local builds sing the frameSrc for the API spec, the credential block doesn't render. When I comment that out, the credential block does render. I guess that means the credential block only supports the <RedoclyAPIBlock> for the API reference.

@github-project-automation github-project-automation bot moved this from 📋 Needs Review to 🏁 Done in Commerce - Pull Requests Jul 18, 2025
@jeff-matthews
Copy link
Contributor Author

As discussed, OpenAPI v3 is a requirement and we're stuck at v2 for ACCS. We will pursue implementation on the Catalog Data Ingestion REST API while we work with product and engineering to prioritize an upgrade for ACCS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request internal Differentiates work between community and Adobe staff major-update Significant updates to content
Projects
Status: 🏁 Done
Development

Successfully merging this pull request may close these issues.

1 participant