> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/support-and-reference/troubleshooting-and-support/errors-handing/307-vs-327-vs-410.md).

# 307 vs 327 vs 410

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva in the Help Center for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this page when `order.do` fails because booking data may be incomplete, invalid, or formatted incorrectly.

### Short answer

`307` means one or more booking request fields are invalid.

`327` means passenger information does not satisfy the booking requirements.

`410` means the contact phone format is invalid.

All three are input problems.

None should trigger a blind retry.

### FAQ

#### What does `307` usually mean?

It means Atlas found an invalid order field.

Check the response `msg` for the exact field.

#### What does `327` usually mean?

It means required passenger or document data is missing or does not meet the current booking requirement.

Recheck `bookingRequirement` from `verify.do`.

#### What does `410` usually mean?

It means the contact phone format is wrong.

Fix the format and resubmit.

### Core difference

#### `307` — invalid booking request parameter

**What it usually means**

One or more request fields are invalid.

This can include passenger fields, document fields, or ancillary mapping.

**Typical examples**

* invalid passenger name
* wrong birthday format
* wrong gender value
* invalid document expiry format
* inconsistent baggage mapping

**Next action**

Read the returned `msg`.

Fix the exact field and resubmit.

#### `327` — passenger information does not meet requirements

**What it usually means**

The request does not satisfy the current `bookingRequirement`.

A required passenger or document field is missing, incomplete, or not acceptable.

**Typical examples**

* missing document data
* missing nationality or residence data when required
* passenger details do not match the required field set for the airline

**Next action**

Re-read `bookingRequirement` from the latest verify response.

Then rebuild passenger data from that requirement.

#### `410` — invalid contact phone format

**What it usually means**

The contact phone format is wrong.

**Expected pattern**

Use `XXXX-XXXXXXXX`.

Examples:

* `0001-87291810`
* `0086-13928109091`

**Next action**

Correct the phone format and resubmit.

### Quick decision rule

Use this rule in production:

* `307` — inspect the exact invalid field
* `327` — recheck `bookingRequirement`
* `410` — fix phone formatting only

### What to check first

When these errors appear, check:

* latest `bookingRequirement`
* passenger name, DOB, gender, and document fields
* contact phone format
* whether the request was built from stale verify data

### Common mistakes

#### Treating `327` like a generic format issue

Do not do this.

It usually means the request does not meet the airline-specific required field set.

#### Treating `410` like a passenger-data problem

Do not do this.

It is a contact formatting problem.

#### Retrying `307` without reading `msg`

Do not do this.

The returned field hint is the fastest path to a fix.

### Best practice

Build `order.do` from the latest verify response.

Use `bookingRequirement` as the source of truth for required passenger and document fields.

Normalize contact phone formatting before sending the request.

### Related pages

* [Verify vs Order](/api-document/product-guides/booking/booking-overview/booking-decisions/verify-vs-order.md)
* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)
* [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)
* [Verify, Order & Ticketing Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/verify-order-and-ticketing-errors.md)