Upcoming Update to Pagination URL Encoding in relevant API Endpoints

[chrisb]

Hello everyone,

We’d like to inform you about an upcoming change to our API that improves compliance with URL encoding standards (specifically RFC 3986) for pagination URLs. This change aims to ensure consistency across all endpoints.

What’s Changing?

A few endpoints currently apply partial URL encoding to the pagination URLs—only encoding the page[cursor] value—rather than fully encoding the entire query string.

We’re updating the following endpoints to encode all query parameters in the pagination URLs fully:

• resource_language_stats: only the Get resource language stats collection GET /resource_language_stats endpoint
• resource_string_comments: only the List resource string comments GET /resource_string_comments endpoint

Previous Format Example:

resource_language_stats?filter[project]=o:<ORGSLUG>:p:<PROJECTSLUG>&page[cursor]=WzEsIFsiOTg1IiwgIjIxIl1%3D

New Format Example (fully URL-encoded):

resource_language_stats?filter%5Bproject%5D=o%3A<ORGSLUG>%3Ap%3A<PROJECTSLUG>&page%5Bcursor%5D=WzEsIFsiOTg1IiwgIjIxIl1%3D

When Will This Change Happen?

The new encoding format will take effect on July 28th, 2025. Please review your implementation and make any necessary adjustments to ensure compatibility.

If you have any questions or encounter issues after the change, please contact our support team.

Thanks for your attention,
— The Transifex Team

[jamorgan]

OK, how can this be tested ahead of the cutover date (Jul 28) ?

[jhonnmick]

Thanks for the clear heads-up, Chris! This change will definitely help with consistency across integrations—already prepping my endpoints.

[chrisb]

Dear jamorgan,

If you’d like to check the changes that will take place, you can send a request to the /resource_language_stats endpoint for example. In the response payload, you should receive a next URL—unless there’s too little data available.

You can then adjust the query parameters as described in the Community post and use that URL to retrieve the next batch of results from the API. If everything is set up correctly, you should receive a valid response.

Keep in mind to use the generated cursor “value” from your original response and not the one from the example on community.

[muthupandi_krishnasa]

Hi Chris, do we also need to encode the next URL from the response as well, or will that automatically be handled starting July 28th?

[chrisb]

Hello dear muthupandi_krishnasa,

The responses you get from the system will be handled by us. It is an update we make and the system will send the urls encoded by default.

You will not have to handle anything.

[muthupandi_krishnasa]

Hi Chris,
I’m still receiving the plain next URL in the response — it appears to be unencoded.

[chrisb]

Hello dear muthupandi_krishnasa ,

Could you please share with us a screenshot from the response you got and from which endpoint?

[muthupandi_krishnasa]

Next URL

End point

[chrisb]

Thank you.

So the endpoint you used is not from the two endpoints we mentioned on our post.

No other endpoints needed the adjustment we introduced here.