AI Translation API: Add Reviewed Text Translation to Your Website

Define what the translation feature should do

An AI translation API accepts text and instructions, then returns a generated translation. For a website team, that could mean drafting an Arabic product description from approved English copy, translating a help paragraph, or preparing an English version of a delivery notice.

Choose a narrow job first. Specify which text enters the workflow, which language should come out, and who approves it. Gammal Tech provides general text AI that you can instruct to translate supplied content. This does not establish specialist translation certification or guarantee that every sentence will be accurate.

The request does not automatically crawl your website, update product pages or publish a second language version. Those are separate website functions. This workflow covers text, without assuming document extraction, image recognition, audio transcription or native mobile app support.

Provide the context a translator would need

A short source string can be ambiguous. “Charge” could describe a payment, a battery action or an instruction. Tell the assistant whether it is translating a checkout label, a support answer or an electronics description.

For a Saudi store, an Arabic brief might request clear Modern Standard Arabic with familiar retail wording such as التوصيل and المتجر الإلكتروني. An English brief might request concise customer-facing English. Specify the language explicitly instead of inferring it from a visitor's name, location or account.

• Purpose: the page or interface element where the text will appear.
• Audience: the reader's likely knowledge and the level of explanation needed.
• Tone: helpful and direct, without adding promotional claims.
• Output: translated text only, or a draft plus separate notes for review.

Translate from approved source copy. A fluent translation cannot resolve contradictory delivery promises or missing product specifications.

Protect product codes, prices and dates

Identify values that must survive unchanged before sending the request. These often include product codes, quantities, links and placeholders. Also define how the translation should handle numbers, currency labels and dates.

A date such as 10/11 is ambiguous without a known format. Resolve that ambiguity in the source first. Instructions help, but your website should still validate protected values and flag missing or altered ones for review.

Create a small, usable glossary

A glossary makes recurring terms more consistent. Start with the names of your products, membership levels and frequently used interface actions. Include a short context note when an Arabic or English word has several possible meanings.

Use terms that match your actual policy. “Return” and “exchange” are not interchangeable if the business handles them differently. Supply the relevant glossary entries with each translation task rather than assuming the assistant remembers a previous session.

Also set length expectations for buttons and cards. A translated label may occupy more space, so review it in the interface instead of judging it only in a text editor.

Connect the text request to a website workflow

For an authenticated Gammal Tech website integration, the documented GammalTech.ai.ask(message, options) method accepts a message and instructions through system_prompt, and returns a string. A translation feature can supply the source text as the message and the translation brief as instructions.

Treat this as an instruction to test, not a guaranteed safeguard. Keep credentials, private business information and unrelated customer data out of browser-side prompts. Render the returned translation as text; do not treat generated markup as trusted page code.

Gammal Tech uses allowed website domains instead of API keys. Use the documented website setup before adding the translation action, and keep approval and publishing under your application's control.

Review meaning and layout before publishing

Place source and translation side by side for an editor. Check factual details first, then meaning, tone and readability. For Arabic output, inspect right-to-left layout alongside mixed-direction content such as codes, prices and English brand names.

1. Compare product features, exclusions, quantities and delivery conditions.
2. Confirm protected strings and glossary terms survived the translation.
3. Read the draft naturally, checking whether pronouns and references remain clear.
4. Preview the actual button, card or paragraph at narrow screen widths.
5. Approve a specific version before the website publishes it.

Use qualified review for text where a mistake could materially affect a person's decisions, including legal terms or health-related instructions. If source content changes, mark the previous translation for another review. Record which source version produced each approved translation.

Count requests when planning translation usage

One AI call is a request, not a translated page or an unlimited editing session. A first draft, a shorter revision and a second-language draft can require separate calls.

Gammal Tech provides 200 free signed-in AI calls per project per month. Signed-in calls beyond that allowance cost 0.20 EGP each. In an editor-only translation feature, the editor needs to be signed in; approving the developer account does not automatically sign in website users.

Guest AI calls have no free allowance and cost 0.40 EGP each. The first guest call also consumes all remaining monthly free signed-in calls for that project. Account for this behavior before adding a public translation button to a project used by signed-in editors.

Questions about AI website translation

Will the API translate every page automatically?

No. Your website must select and supply the source text. Choosing pages, storing translations, approving versions and publishing them are separate parts of your implementation.

Can I reuse a translation after approval?

Your application can store approved content and display it again. Track its source version so a later product or policy change does not leave an outdated translation on the page.

Does Arabic support guarantee local wording is correct?

No. Specify audience, terminology and tone, then ask a suitable reviewer to assess the result. Local context improves the brief; review establishes whether the particular draft is ready to publish.