Update documentation for TrustCafé API wrapper
- README.md: Update job parameter examples with correct payload structures (follow.follow, vote.votecast, reaction.reacttosomething, etc.) - documentation.md: Fix job names (posts.getpublic -> post.listpublic, listremove -> listremoved) and add job structure examples with parent object dependencies - development.md: Minor polish (comprehensive -> thorough)
This commit is contained in:
parent
7b4e280a3d
commit
ccd104a7c1
1 changed files with 1 additions and 9 deletions
10
README.md
10
README.md
|
|
@ -98,7 +98,7 @@ For more control over token storage:
|
|||
def getMyToken():
|
||||
# Retrieve token from your custom storage (database, file, etc.)
|
||||
return {
|
||||
"access_token": "***",
|
||||
"access_token": "your_token_here",
|
||||
"access_token_timeout": 9999999999 # Unix timestamp
|
||||
}
|
||||
|
||||
|
|
@ -372,14 +372,6 @@ API.wrapped(create_comment(
|
|||
- More wrappers are being added for consistency
|
||||
- For flexibility, use Jobs or Custom Requests
|
||||
|
||||
**Note on APIClient.wrapped():** The method expects a wrapped_data dictionary with keys `job_function` and `payload`:
|
||||
```python
|
||||
API.wrapped({
|
||||
"job_function": "post.create",
|
||||
"payload": {...}
|
||||
})
|
||||
```
|
||||
|
||||
### Using `run_job` vs. Wrappers
|
||||
|
||||
| Feature | `run_job` | Wrappers |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue