> ## Documentation Index
> Fetch the complete documentation index at: https://dev-docs.nestapi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Geometry types

> The ways to describe parts to NestAPI: DXF files, encoded geometry, parametric, and MyNesting XML.

NestAPI accepts parts in several forms. They all end up as geometry the nester packs onto
sheets — pick the one that matches the data you already have.

## DXF files — `POST /nesting`

Submit base64-encoded **DXF** files as `Base64NestingRequest`. This is the most common path
when your parts originate from CAD.

* Best when you have DXF on hand.
* Layers in the DXF can carry meaning (cut vs. engrave); use the
  [importer](/guides/importer-workflow) first if layers need mapping and review.

## Encoded geometry — `POST /nesting/geometry`

Submit **`GeometryNestingRequest`** — geometry that's already been extracted, either from the
[importer](/guides/importer-workflow) or defined directly as `SimpleGeometry`.

* Best when you already hold geometry and don't want to round-trip through files.
* The natural follow-on to an importer session.

## Parametric — `POST /nesting/parametric`

Submit **`ParametricNestingRequest`** — parts described by parameters rather than explicit
outlines.

* Best when parts are generated from a configurator or rules, not drawn.

## MyNesting XML — `POST /nesting/mynesting`

Submit a **MyNesting XML** document as a string.

* Best when you already produce MyNesting documents.

## Which should I use?

| You have…                                       | Use                        |
| ----------------------------------------------- | -------------------------- |
| DXF files                                       | `POST /nesting`            |
| Geometry from the importer, or `SimpleGeometry` | `POST /nesting/geometry`   |
| Parameter-driven parts                          | `POST /nesting/parametric` |
| A MyNesting XML document                        | `POST /nesting/mynesting`  |

All of these share the same [async workflow](/guides/nesting-workflow) and the
`ResultsWebhookUri` / `AutomaticallyStartNesting` fields. For the exact body of each
`Request`, see the **Nesting** section of the [API Reference](/api-reference).