From 3f01592a06f085023a70ca6443af4d3124833e47 Mon Sep 17 00:00:00 2001 From: Jean Potier Date: Sun, 20 May 2018 21:50:20 +0300 Subject: [PATCH] Update nullable of url in Status (#622) https://bidule.menf.in/api/v1/statuses/82725 is an example of a valid status even though it contains a null url field. Either my application should reject this, or the API should explicitely allow it. --- Using-the-API/API.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Using-the-API/API.md b/Using-the-API/API.md index af18d7b2..ec8977c9 100644 --- a/Using-the-API/API.md +++ b/Using-the-API/API.md @@ -927,7 +927,7 @@ The most important part of an error response is the HTTP status code. Standard s | ------------------------ | ----------------------------------------------------------------------------- | -------- | | `id` | The ID of the status | no | | `uri` | A Fediverse-unique resource ID | no | -| `url` | URL to the status page (can be remote) | no | +| `url` | URL to the status page (can be remote) | yes | | `account` | The [Account](#account) which posted the status | no | | `in_reply_to_id` | `null` or the ID of the status it replies to | yes | | `in_reply_to_account_id` | `null` or the ID of the account it replies to | yes |