Identifer Retrieval

[old jay]

Nope

[tough citrus]

do u plan to ever offer anything of the sort or some type of Developer API?

[old jay]

Yes, next big update

[tough citrus]

are u possibly able to give some information on what the api will include so i can plan ahead?

[old jay]

No idea

[tough citrus]

haha okay last question. do you have a ideal release date for the api

[old jay]

Nope

[tough citrus]

okay well thank you for all the help

[old jay]

[wide cairn]

Hey @tough citrus ,

Been working on a third-party txAdmin api, it’s still in the works but already has some nice features. Feel free to check it out below;

https://github.com/NickTacke/txApi

If you have any questions/suggestions please let me know

[stray stump]

this seems like a terrible idea

since there's 0 security on it

[old jay]

Tabarra approved

[stray stump]

doesn't mean I have to like how sketchy the security on it is lol

[wide cairn]

It’s only usable via exports in server scripts

And if you have something malicious in your server scripts you’re doing something wrong anyways

But suggestions for improvements are always welcome

(Repo description doesn’t say “sketchy FiveM resource” for no reason )

[stray stump]

that's valid

[wide cairn]

But what would you add to make it more secure?

[stray stump]

well ideally , the perfect solution would be the one baked into monitor , so that there can be specific permissions per resource, and execution validation

[wide cairn]

And assuming I’d like to keep it separated, a whitelist to GetInvokingResource?

Maybe some logging to a file?

Rate limit?

Don’t forget the input is still getting validated on the backend

These are public paths anyone with access to the txAdmin site can access

[stray stump]

yeah , that's true