Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form below and we will reply as soon as possible.

  • Appcues Certifications & Training
  • Integration Hub
  • Contact Us
  • Docs home
  • Web Experiences
  • Customization & Styling

Upload Translations Manually

Learn how to manually upload translation tables per Flow via the Appcues API.

Updated at July 2nd, 2024

Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form with the details about the help content you'd like to see.

  • Installation & Developers
    Installing Appcues Web Installing Appcues Mobile API & Data Troubleshooting Extras
  • Web Experiences
    Building Web Experiences Targeting Studio Customization & Styling Use Cases Troubleshooting FAQ
  • Mobile Experiences
    Installation & Overview Building Mobile Experiences Mobile Analytics & Integrations Troubleshooting
  • Workflows
    Building & Configuration Use Cases Workflow Analytics and Integrations
  • Account Management
    Subscription Users & Data
  • Analytics
    Experience and Event Analytics Data
  • Best Practices
    Best Practices Use Cases Pro Tips Product-led Growth
  • Integrations
    Integration Documents Use Cases Extras
  • System Status
    System Status & Incidents
+ More

Table of Contents

Get your auth token Get your account ID Get your flow ID Prepare your translations Upload files to the Appcues translation upload endpoint

This article describes how to manually upload translation tables per flow via the Appcues API.

Get your auth token

  • Log into studio.appcues.com.
  • Open the JavaScript console (Cmd-Shift-J on Mac, Ctrl-Shift-J elsewhere).
  • Enter the following command and hit Return:
await window.apc_auth.getCurrentCustomToken()
  • The command will return a very long character string, enclosed in quotes. Copy the contents (not the quotes). This is your auth token. As an example:
ABC.123.XYZ

Get your account ID

You can find your account ID on the Account Settings page: https://studio.appcues.com/settings/account

We'll use 12345 as an example.

Get your flow ID

You can find the flow ID from the flow's URL in studio.appcues.com. We'll use https://studio.appcues.com/journeys/-L9876543210 as an example URL, making our flow ID -L9876543210.

Prepare your translations

We'll use the example filename translations.json. This API endpoint accepts uploads in either CSV and JSON format.

Upload files to the Appcues translation upload endpoint

Using all the example values mentioned previously, here is an example of an upload request, using the curl command-line HTTP client (installed by default on Mac, widely available):

curl -X POST -v \
     -F file=@translations.json \
     -H 'Authorization: Bearer ABC.123.XYZ' \
     https://customer-api-main.prod.us-west-2.aws.appcues.net/v1/accounts/12345/flows/-L9876543210/translations

On success, the API will return a 200 OK status code, also returning the uploaded and parsed translation in the response.

translation upload manual upload

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • HTTP API (Developer)
  • Appcues Installation Overview
  • Required Cookies, Local Storage, and Session Data
  • Manually Install the Builder Extension
Appcues logo

Product

Why Appcues How it works Integrations Security Pricing What's new

Use cases

Appcues Integration Hub User Onboarding Software Feature Adoption Software NPS & Surveys Announcements Insights Mobile Adoption

Company

About
Careers

Support

Developer Docs Contact

Resources

The Appcues Blog Product Adoption Academy GoodUX Case studies Webinar Series Made with Appcues Appcues University

Follow us

Facebook icon Twitter icon grey Linkedin icon Instagram icon
© 2022 Appcues. All rights reserved.
Security Terms of Service Privacy Policy

Knowledge Base Software powered by Helpjuice

Expand