[GH-ISSUE #218] How to get a real requests.models.Response vs a string / json ? #123

Closed
opened 2026-02-27 15:46:33 +03:00 by kerem · 1 comment
Owner

Originally created by @arLevi on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/218

Hi
I need some help receiveing the raw response in order to continue the flow, I'm using this line

res = proxmox('/path/to/qemu/100/clone').post(**params)

Which work OK, but I receive the response as a string - therefor,
I cannot understand what my response status code was in order to continue my automation.

Response type:  <class 'str'> 
Response value: UPID:my-proxmox:001E..:qmclone:100:myuser@pam!:mytoken

Is it possible to receive the raw response vs a digested response ?
Something that its type will be:

Response type: <requests.models.Response>

So I will be able to fetch what I need like:

res = proxmox('/path/to/qemu/100/clone').post(**params)
res.status_code
res.json()

etc... ?
any ideas ?

Originally created by @arLevi on GitHub (Jan 28, 2026). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/218 Hi I need some help receiveing the raw response in order to continue the flow, I'm using this line ``` res = proxmox('/path/to/qemu/100/clone').post(**params) ``` Which work OK, but I receive the response as a string - therefor, I cannot understand what my response status code was in order to continue my automation. ``` Response type: <class 'str'> Response value: UPID:my-proxmox:001E..:qmclone:100:myuser@pam!:mytoken ``` Is it possible to receive the raw response vs a digested response ? Something that its type will be: ``` Response type: <requests.models.Response> ``` So I will be able to fetch what I need like: ``` res = proxmox('/path/to/qemu/100/clone').post(**params) res.status_code res.json() ``` etc... ? any ideas ?
kerem closed this issue 2026-02-27 15:46:33 +03:00
Author
Owner

@jhollowe commented on GitHub (Jan 29, 2026):

see #217

<!-- gh-comment-id:3815357226 --> @jhollowe commented on GitHub (Jan 29, 2026): see #217
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxmoxer#123
No description provided.