Skip to main content
Solved

Unable to trigger transformations through Playground API

  • December 8, 2021
  • 1 reply
  • 58 views

Christian Dalen
Active

 

Since last week, I have not been able to trigger any transformations via the Playground API.

({{baseUrl}}/api/playground/projects/{{project}}/transformations/:id/run)

I am getting :

404 Not found

with response body: 

{"code":4

(Yes; a incomplete json)

I noticed also that the API has now been included in API v1. Is maybe this error related to this change?

Related (?):

I can see that when I run a “GET” using the new endpoint, I get the same error ({"code":4). Have you been a bit quick in the implementation and running a GET on the v1 API from the playground API?

 

I can also mention that it does actually work using the new v1 endpoint, so this will solve the problem. My problem is, off course, that I am currently using the Playground API which is currently failing and I have to replace the logic and test/release it (Taking extra time).

Working Example:

POST {{baseUrl}}/api/v1/projects/{{project}}/transformations/run

The example from Postman is with externalId, so you will have to replace it with “id” for it to work with the TransformationId:

Body:

{

    "id":<transformationId>

}

 

Best answer by Emel Varol

Hello Christian, thanks for your question!

We removed the endpoints supporting only “id”s. Playground API is more like an experimental one so changes might happen there. 

But, we have the methods documented in v1  available in playground API for now (playground is a mirror of v1 at the moment, please refer to v1 documentation).  So you can start using the working example on playground as well but we strongly recommend you to start using our stable API (v1). 

View original
Did this topic help you find an answer to your question?

1 reply

Emel  Varol
Practitioner
  • Practitioner
  • 4 replies
  • Answer
  • December 8, 2021

Hello Christian, thanks for your question!

We removed the endpoints supporting only “id”s. Playground API is more like an experimental one so changes might happen there. 

But, we have the methods documented in v1  available in playground API for now (playground is a mirror of v1 at the moment, please refer to v1 documentation).  So you can start using the working example on playground as well but we strongly recommend you to start using our stable API (v1). 


Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings