Marketo deprecated Swagger URL | Community
Skip to main content
S
swati2868negi
Level 1
March 2, 2026
Question

Marketo deprecated Swagger URL

  • March 2, 2026
  • 1 reply
  • 38 views

HIGH PRIORITY: Blocker – CASDK-0005 Error in Marketo.
 
Dear Adobe Support Team,
 
I hope you are doing well.
 
We are currently experiencing a critical blocker issue related to Marketo API’s . We request your urgent assistance.
 
Marketo Instance Details:

Munchkin ID: 186-DAI-284
 
We are encountering error code CASDK-0005, and the following error appears in the logs:
 
java.io.FileNotFoundException: https://developer.adobe.com/marketo-apis/swagger-mapi.json
 
It appears that the adapter is attempting to access the above Swagger endpoint, which is no longer accessible. However, we were unable to locate the currently supported Swagger URL in the Adobe Experience League documentation.
 
Could you please provide:

1. The correct and currently supported Swagger JSON URL for the Marketo MAPI APIs

2. Confirmation whether the below Swagger reference is the appropriate and supported file to use:
 
Document: https://developer.adobe.com/marketo-apis/api/mapi#tag/Activities

Swagger URL: https://raw.githubusercontent.com/AdobeDocs/marketo-apis/main/static/swagger-mapi.json
 
1. The official deprecation date of the previous Swagger endpoint

2. Any related release notes or formal deprecation announcement
 
Since due to this issue we are facing issue in our production environment, we kindly request expedited support and clarification at the earliest possible time.
 
We look forward to your prompt response.
 
 
Kind regards,

Swati
 

1 reply

Darshil_Shah1
Community Advisor and Adobe Champion
Darshil_Shah1Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 2, 2026

The error you're seeing is most likely related to the old Swagger reference being moved, not a Marketo API outage. The endpoint: https://developer.adobe.com/marketo-apis/swagger-mapi.json is no longer valid. Adobe reorganized the Marketo developer documentation under the new Developer site structure, and some older Swagger URLs stopped resolving. The GitHub-hosted Swagger file you mentioned is currently the closest thing to the maintained reference. 

 

However, it's important to note that Marketo APIs themselves do NOT depend on the Swagger endpoint; Swagger is only for documentation. If your connector is failing because it requires the Swagger file at runtime, that usually indicates a dependency configuration issue in the connector rather than a Marketo platform problem. Marketo REST APIs should still work normally using the standard endpoints like: https://{instance-base-url}/rest/v1/activities.json. If this was previously working, it likely means the connector or SDK is hardcoded to the old Swagger URL -- you'd want to update it so it directly calls Marketo API endpoints with your instance base URL.

 

Also, as an FYI, this is the Marketo Engage community. If you want to chat with Adobe Customer Support, you'd have to raise a support ticket from your instance (Hele Center > Support > Open Ticket).

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    March 2, 2026

    I'm struggling to imagine any situation where hitting a remote Swagger URL from your production env would be advisable. Even if the Swagger file were accessible, it wouldn't necessarily be the same version you built your code against!

      Darshil_Shah1
      Community Advisor and Adobe Champion
      Darshil_Shah1Community Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      March 2, 2026

      I echo Sandy! Ideally, the Swagger file shouldn’t be fetched every time dynamically from a remote URL in production. The GitHub file works, but it’s intended primarily as a documentation/reference artifact, NOT as a runtime dependency. That’s also why the previous developer.adobe.com/swagger-mapi.json endpoint disappeared without much notice. As a best practice, the production system should not depend on external documentation URLs that may change.

        Terms & ConditionsAccessibility statement

        Loading footer...