APIDays Paris 2026 brought together API practitioners from across Europe to discuss REST, GraphQL, AsyncAPI, and gRPC design patterns. UUID adoption was a recurring theme — particularly the operational advantages of switching from auto-increment integers to UUID v7 primary keys exposed in APIs. See UUID in OpenAPI for the schema details.
Session highlights
UUID v7 as an API cursor
The highest-attended UUID session covered cursor pagination using UUID v7 as the page token:
# OpenAPI 3.1 — cursor pagination with UUID v7
/orders:
get:
parameters:
- name: after
in: query
schema:
type: string
format: uuid
description: UUID v7 cursor — returns orders created after this ID
example: "018fbe3a-4c5d-7b12-8abc-0123456789ab"
- name: limit
in: query
schema:
type: integer
default: 20
maximum: 100
responses:
"200":
content:
application/json:
schema:
type: object
properties:
data:
type: array
items: { $ref: '#/components/schemas/Order' }
next_cursor:
type: string
format: uuid
nullable: true
UUID v7 cursors are self-describing — next_cursor encodes when the last item was created. See UUID v7 for Cursor Pagination for the full SQL pattern.
GraphQL ID scalar with UUID v7
# Schema — ID scalar maps to UUID v7 string
type Order {
id: ID! # UUID v7 string
customerId: ID! # UUID v7 string
status: String!
createdAt: DateTime! # still useful for display, not for queries
}
type Query {
order(id: ID!): Order
orders(after: ID, first: Int): OrderConnection!
}
// Resolver — validate UUID format on input
import { validate, version } from 'uuid';
const resolvers = {
Query: {
order: async (_: unknown, { id }: { id: string }) => {
if (!validate(id)) throw new Error('Invalid UUID');
return db.orders.findById(id);
},
},
};
See UUID in GraphQL and UUID v7 in GraphQL Subscriptions for the full pattern.
Idempotency keys in REST APIs
Stripe-style idempotency keys using UUID v4 (not v7 — session explicitly noted the security argument for v4 here):
# OpenAPI header parameter
parameters:
- name: Idempotency-Key
in: header
required: false
schema:
type: string
format: uuid
description: >
UUID v4 for idempotency — retry the same request safely.
The server deduplicates requests with the same key within 24h.
// Express middleware — idempotency key deduplication
app.use(async (req, res, next) => {
const key = req.headers['idempotency-key'] as string;
if (!key) return next();
const cached = await redis.get(`idem:${key}`);
if (cached) return res.json(JSON.parse(cached));
res.on('finish', () => {
redis.setEx(`idem:${key}`, 86400, JSON.stringify(res.locals.body));
});
next();
});
Further reading
- UUID in OpenAPI — schemas and validation
- UUID v7 for Cursor Pagination
- UUID as Idempotency Keys
- UUID in GraphQL
- UUID v7 in Microservices — correlation IDs
External references
Frequently asked questions
What UUID version was recommended for REST API primary keys at APIDays Paris 2026?
UUID v7 was the consensus recommendation for new APIs. The 48-bit timestamp prefix means the ID itself is a monotonic cursor, enabling WHERE id > $cursor ORDER BY id keyset pagination without a separate timestamp field. For user-facing IDs in public URLs, speakers recommended UUID v4 or encoding UUID v7 with Base64url to hide the timestamp. See UUID v7 for Cursor Pagination and UUID Security.
How should UUID fields be defined in OpenAPI 3.1 schemas?
Use type: string with format: uuid. OpenAPI 3.1 does not distinguish v4 from v7 in the format string — document the version in the description field: description: "UUID v7 — time-sortable, millisecond precision". Add an example with a real UUID v7 value. Use pattern for strict validation if your toolchain supports it. See UUID in OpenAPI — schemas and validation.