Understand a content record
An article and its Wallkit record serve different purposes. City Journal publishes “City Hall budget explained” on its website. Wallkit holds recorded information about that item so the integration can identify it and check access for a reader.
The Content table shows the recorded metadata. It does not show the article body or provide a content detail editor.
Read the visible columns
| Column | What it tells you |
|---|---|
| Title | The recorded title. When a link is stored, the title opens that URL in a new tab. |
| Price | The recorded content price and currency. This column includes price controls; viewing a price is not evidence of a purchase or payment. |
| Content type | The recorded type, such as article. This is separate from an article's categories or tags. |
| Taxonomies | Classification names; click a populated cell to expand the term names. |
| Created at | When the Wallkit content record was created, not when the publisher made the article public. |
Use Find a content item to narrow the list. Read the table without changing its price controls when your task is only to inspect the record.
Keep the identifiers straight
Imagine the integration owner identifies this article as follows:
| Information | Fictional example | Meaning |
|---|---|---|
| Publisher article URL | https://example.com/articles/city-hall-budget | Where the article is served on the publisher's site. A stored link can appear through the Title column. |
| Content key | city-journal-204 | The stable item key supplied by the publishing integration within the selected publication/resource. Admin offers a Key filter. |
| Internal numeric ID | 204 | Wallkit's record ID. It is distinct from the content key and is not shown as a Content table column. |
A similar title or URL is not enough to confirm identity. Use the intended publication and content key with your integration owner. The example key and numeric ID are different kinds of identifier even though both happen to contain 204.
Information managed through integration
The current table does not expose every stored field. Description, images, extra metadata, update/publication dates and the underlying classification keys are information for the integration owner to inspect through the relevant technical interface. They are not additional controls or tabs in this table.
Registration and updates depend on your integration's chosen path. For example, the documented register-and-check path can create a missing item, but does not overwrite an existing item's metadata from the supplied creation fields. Do not assume that editing a CMS article immediately updates Wallkit, or that changes made in Wallkit update the website.
If a title, link or classification looks old or wrong, share the intended publication, content key, article URL and expected value with the integration owner. They can confirm which record and update path the integration uses. Developer Central's content walkthrough explains registration, metadata and reader access checks.
What this record does not establish
A record identifies content Wallkit knows about. Publishing, reader payments and access are handled separately. For a payment question, read the transaction. For article access, the integration uses the reader's context and applicable rules to obtain an access decision.
Continue to Understand categories, tags and authors, or read Understand content access rules for Plan selection and limits.