# Wikiup API > Wikiup manages hospitality properties, rooms, reservations, guest communications, payments, and hosted booking widgets. Use the API reference for current request fields, permissions, enum values, and response shapes. ## Start here - [API reference](https://api.wikiup.app/): Searchable endpoint reference and integration workflows. - [Programmatic account setup](https://api.wikiup.app/#programmatic-setup): Email verification, first API key, property selection, and first scoped request. - [AI onboarding instructions](https://api.wikiup.app/ai-onboarding.md): Step-by-step setup for an assistant working with a human account owner, including credential handling and key rotation. - [Channel management](https://api.wikiup.app/#channel-management): White-label sandbox channel setup, versioned pricing acceptance, hotel room and rental imports, room/rate mapping, booking revision handling and reviewed inventory publishing. Production activation is blocked. - [Complete channel API workflow](https://api.wikiup.app/channel-management-api.md): Console-independent owner API-key workflow, pricing, custom callbacks, preview authorization, Vrbo verification, multi-listing mapping, imports, activation, sync, review, explicit approval, pause, removal and retries. - [Wikiup Console](https://console.wikiup.app/): Interactive account setup, property management, sign-in, and account recovery. ## Listing partners - [Affiliate integration](https://api.wikiup.app/hidden-san-diego-integration.md): Date-free area catalog, lazy availability, listing detail and attributed booking. - [Card metadata](https://api.wikiup.app/listing-card-metadata.md): description, tagLine (100 characters), stayType, starRating and priceTier. Catalog description is an excerpt; direct content retains its full description. - [Public locations](https://api.wikiup.app/listing-locations.md): Exact latitude/longitude pair or null; no approximate positions. - [Affiliate management response schemas](https://api.wikiup.app/affiliate-management.schema.json): Account, blacklist, optional ratings and income fields; use the matching named definition. - [Staff response schemas](https://api.wikiup.app/staff-responses.schema.json): Reservation timeline, unpaid balances, mailbox messages, knowledge review and equipment readings. These do not grant affiliate access. - [Response schemas](https://api.wikiup.app/travel-listings.schema.json): Machine-readable response definitions. - [Rollout verification](https://api.wikiup.app/listing-card-rollout-verification.md): Checked revision, timestamps, live versus mocked evidence and deployment limits. Verify target deployment before consuming a renamed field. ## Environments Production API: https://api.wikiup.app Preview API: https://api-preview.wikiup.app Keep each environment's account credentials and property IDs separate. Ask which environment the owner wants before creating resources. ## Authentication A new account can be created through POST /api/accounts/registration followed by POST /api/accounts/registration/confirm. The human must own the inbox and supply the emailed one-time code. Confirmation returns the first API key once. Never request an email account password. Server-side integrations send Authorization: Bearer . Property resources generally also require x-property-id: . List accessible memberships with GET /api/properties before selecting or creating a property. Keys are constrained by current membership permissions, read_only/read_write access, an optional property allowlist, and expiration. Store full keys in a server-side secret store. Do not print them, commit them, send them to a browser, or include them in a final answer. GET /api/api-keys returns metadata only. Key listing and issuance require an interactive account session; no API key may manage another key, although a valid key may revoke itself. Use Console → API keys to issue restricted credentials and rotate them. Account/profile/password, connected mailbox messages, Google email connect/disconnect, property deletion, membership departure, all /api/team operations (including read-only summaries), and invitation acceptance require an interactive session. ## Integration rules Use the documented fields and enum casing exactly. Public widget booking endpoints and reservation-scoped guest sessions are separate from staff API keys. A payment intent alone does not confirm a booking. Review cancellation quotes before confirming financial changes. Do not infer that deleting a reservation executes a refund. New-property channel import: GET/POST /api/channel-management/property-import (start, save_details, import_room, finish, cancel); supports hotels and rentals, owner-bound resumable provisional properties, closed-sales activation. Full contract: /channel-management-api.md. ## Isolated staging data for PMS integrations Read [Staging test data](https://api.wikiup.app/staging-test-data.md) for the owner-authorized API setup, Booking CRS prepare/create/modify/cancel/verify commands, delivery states, errors and safe retry rules. Preview can reach real OTA accounts; use a separate property with zero connected channels. Main channel sync is not the ingestion-only verification endpoint. - Affiliate ratings CRUD and optional fetch=ratings: /affiliate-listing-ratings.md (see rollout status). Destination IDs and compatibility: /travel-destinations.md