API for Multiple Language

Hello, I have enabled Multiple Languages through Manage > Languages. 

But I failed to find relevant parameter to retrieve translation text in the Checkfront API documentation. 

Please help. Thanks.


  • Hi NG,

    Thanks for writing into the Checkfront forums.

    Unfortunately, the API doesn’t currently work with the multi-language feature.

    However, I’ve put in a feature request with our product team to evaluate on whether to add the functionality or not.

    You can learn more about how we handle feature requests here:https://www.checkfront.com/how-we-handle-feature-requests

    Please let us know if you have any other questions.

  • Please do so. I think it is a critical feature.

    We are developing our custom frontend using Checkfront API and we chose the Professional Plan in subscription in order to build with multi-language feature.

    For now we cannot retrieve translation text from the API, how about notifications? Any chance we can trigger multi-language notifications when we checkout from our custom frontend? Thanks.
  • edited March 2016

    Hi NG,

    Thanks for your reply.

    In your API requests, you can specify the ‘language’ parameter with the ID of the language you want to use. 

    I’ll be moving this discussion thread over to our Developer section of the forum.

    Hope that helps - let us know if there’s anything else we can do to help and we’ll be happy to assist.

    Kind regards,

    Aaron Brook

    Checkfront Support Team

  • edited March 2016
    Unfortunately, the 'language' parameter probably won't work as expected for the API, which is why it hasn't been made public. Our multiple language feature is tightly coupled to our internal user interface components, but I agree that we should work on making it function through the API where it makes sense to do so.

    NG, can you give us a list of all request endpoints and response keys you'd like to see made translatable? We need to know which fields would be required for translation, before assessing the scope of this change. A list like the following is an example of what we're after.

    • /item/ - the 'name' fields for the item names
    • /item/ - the 'summary' fields for the item summaries
    • /booking/ - the 'status_name' field for the booking status
    • ...


  • We will need translation API to work for: 
    1) building the booking form ( booking/form )
    2) triggering email notifications

    Is point 2 above an available function now? Or are there other work-arounds?
    For other translations we can build it with our front-end.

  • For notifications to work with multi-language translations, the booking needs to be created with this parameter specified; defining this in your booking/create call stores the customer's language in the booking for use with all subsequent notifications where available.
    This endpoint specifically is where the original suggestion to use the parameter was directed -- while it's not yet widely accepted throughout the booking API, it is taken as input for use by the system in newly created bookings. 
  • NG,

    To add to what Kris said, the 'language' parameter should also work for receiving translated booking form labels with the booking/form endpoint.
  • Hi All,

    Have tested the "language" parameter works with the following API:
    • booking/form
    • booking/create
    Thank you.
  • Hello! I found this old discussion, and I also would need some information on how to get multilingual information via the API. I have built a listing that lists the available items. My site is in 3 languages, that I have enabled in the interface. It would be useful to get the name, details and summary of items translated. I tried to call the api with the language parameter, but it does not seem to make a difference.

    (screenshot: http://take.ms/6jrOb ) ( http://www.giroola.com

    Is this something that could be added?  Thank you! 
  • Hi vermario,

    Can you provide an example of the language parameter you used? Are you making a call to the "item" endpoint?

    Also, you'll need to make sure that your item name, description, etc are translated in your account at Manage > Languages > French / Italian.

    Checkfront Developer
  • Hello! Thanks for your answer.

    This is a screenshot of what I get our of the console:  


  • It seems to me that the language is recognised correctly, but the name that I get out of the api call is the english one, and not the one that I added as the italian translation: (Screenshot) https://monosnap.com/file/qo2rDk5bcoO3PLapEq5L7tofXSnDgS ;
    Am I doing something wrong?
Sign In or Register to comment.